New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 604818 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Adobe Flash Player causing pegging the CPU with no tabs open

Project Member Reported by michae...@chromium.org, Apr 19 2016

Issue description

Version: 50.0.2661.79
OS: Chrome

What steps will reproduce the problem?
(1) Notice high fan speed. In task manager, the Browser and GPU Process CPU usage entries are >25%
(2) Close all tabs and apps, twiddle thumbs, still happening
(3) Disable Adobe Flash Player in chrome://plugins, CPU usage drops immediately and fan quiets


Adobe Flash Player - Version: 21.0.0.216-r1
Shockwave Flash 21.0 r0
Name:	Shockwave Flash
Description:	Shockwave Flash 21.0 r0
Version:	21.0.0.216-r1
Location:	/opt/google/chrome/pepper/libpepflashplayer.so
Type:	PPAPI (out-of-process)
 	Disable
MIME types:	
MIME type	Description	File extensions
application/x-shockwave-flash	Shockwave Flash	
.swf
application/futuresplash	FutureSplash Player	
.spl

 
trace_flash.json.gz
713 KB Download
Cc: rohi...@chromium.org ihf@chromium.org hsiangc@chromium.org
michaelpg@ is this reproducible with specific sites or any Flash site?

Could you also add more version and device info? First 5-6 lines from about: page.
I've only noticed this once so far, there wasn't any particular Flash-heavy page open that I can recall, and the issue persisted after closing all tabs.


Google Chrome	50.0.2661.79 (Official Build) beta (64-bit)
Revision	0
Platform	7978.57.0 (Official Build) beta-channel samus
Blink	537.36 (@0)
JavaScript	V8 5.0.71.32
Flash	21.0.0.216-r1
User Agent	Mozilla/5.0 (X11; CrOS x86_64 7978.57.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.79 Safari/537.36

Also a sanitized command line:

/opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=21.0.0.216-r1 --ppapi-flash-args=enable_hw_video_decode=1 --enable-fixed-position-compositing --enable-impl-side-painting --max-tiles-for-interest-area=512 --ui-enable-per-tile-painting --ui-prioritize-in-gpu-process --use-gl=egl --enable-native-gpu-memory-buffers --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --login-profile=user --enable-natural-scroll-default --has-chromeos-keyboard --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/default_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/default_small.jpg --child-wallpaper-large=/usr/share/chromeos-assets/wallpaper/child_large.jpg --child-wallpaper-small=/usr/share/chromeos-assets/wallpaper/child_small.jpg --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-prefixed-encrypted-media --enterprise-enrollment-initial-modulus=14 --enterprise-enrollment-modulus-limit=18 --vmodule=screen_locker=1,webui_screen_locker=1,*ui/display/chromeos*=1,*ash/display*=1,*ui/ozone*=1,*zygote*=1,*plugin*=2,*chromeos/login/*=1 --login-user=redacted@example.com --login-profile=redacted-hash-here --flag-switches-begin --ash-enable-touch-view-testing --flag-switches-end

Comment 3 by ihf@chromium.org, Apr 20 2016

In theory the Flash process should get terminated after a few seconds/minutes of no tabs.
#3: The only reason I closed all my tabs was to see whether a particular tab was causing the issue. Normally I would just go on with my day and be irked that the fan is so loud.

Comment 5 by ihf@chromium.org, Apr 21 2016

Status: WontFix (was: Untriaged)
I looked at the trace. Unfortunately I have nothing actionable here. I'll close it, but please reopen if you have a repro or maybe a feedback report. Thank you!
Ok, thanks. Is there anything else I should do if I notice it again, besides tracing and a feedback report?

Comment 7 by ihf@chromium.org, Apr 21 2016

I am really unable to guess where to problem is. It is a wide field. The chrome trace above doesn't contain ppapi. If it was Flash process itself burning cycles, one needed Flash symbols and run "perf top" to see what Flash actually is doing. Also ps -ef | grep type=ppapi might be interesting, but is already contained in the feedback report. Long story short, this issue really needs a repro. :-(

Sign in to add a comment