Comment #119 on issue 373923 by
m...@tribalvibes.com: Google Chrome Helper
Here's more grist. This is destroying usability for Chrome and my mbp. Hope
these observations help you track it down:
General
1. MBP 8,2 15" quadcore i7 late 2011, ssd, 16gb, 25% avail (for this
test--not paging), AMD Radeon HD 6770M 1024 MB
2. This seems to have started a year ago or so? And getting progressively
worse.
3. Used to keep 200++ tabs and 50+ windows open in Chrome-20 something with
sess buddy. Now dawgs out at 50 tabs and a dozen windows.
4. Not specifically a flash-related video playback issue. Restoring windows
with lots of tabs will do it too, as will HTML5 video.
5. One major version around Chrome 28-ish or maybe it was 32 suddenly was
much better--fast and smooth the way it should run. Could restore dozens of
tabs in a few seconds.
6. Installed Canary (yea!) Seemed better for 24 hours, then recurred.
These tests are with Canary. Similar results with 32 bit Chrome.
7. Wild guess #1: interprocess coms, semaphore, mutex, work or msg queue
lock issue, thread sync, something falling back to a spin lock and starving
while other queues are overstuffed holding the locks
8. Wild guess #2: bad Darwin interaction, timer/wakeup/yield issue,
something should be scheduled on a usec timer but is being scheduled on a
msec timer, debug trace not removed in production build.
9. Wild guess #3: Network request queue interaction. GPU interaction.
Test 1 Video Playback
1. Plugins disabed. Specifically, flash disabled and Shockwave Flash
process killed in Task Manager. Screenshot 1.
2. Play a video. Lets say,
https://www.youtube.com/watch?v=BqfIvPQ8Dgo
3. Watch CPU spike to 100%. loadav > 12. Screenshot 3.
4. kernel_task > 500% Google Helper (Canary) > 50% Screenshot 4. Samples
1 & 2.
5. Poor video performance and system responsiveness destroyed.
6. Pause video, keep tab open. CPU usage drops to ~33% and remains bursty.
Screenshot 6. System may return to quiescent state after ten minutes or
more. Suggests timer/msg queue issue.
7. Close video tab. System returns to quiescent state within ten seconds.
Screenshot 7.
Test 2 Restore Multiple Tabs
8. Open a window with a dozen or more tabs. Say, API docs like
https://developers.facebook.com/docs/graph-api/reference/v2.1/object/likes
and cmd-right-click a bunch of related pages. Screenshot 8.
9. Close window. Cmd-shift-t reopen tabs.
10. kernel_task > 300% and Google Chrome main task > 50%. Screenshot 10.
Sample 3.
11. Watch it spin. Screenshot 11.
12. Takes more than 30 seconds to restore a dozen comparatively simple
pages already cached. Screenshot 12.
System response with Chrome running (even quiescent) is notably sluggish.
Typeahead and app context switching delay, beach ball, etc.
Attachments:
Sample of Canary 39.0.2149.0 Google Chrome Helper 1 play youtube html5
video.txt 657 KB
Sample of Canary 39.0.2149.0 Google Chrome Helper 2 play youtube html5
video.txt 613 KB
Sample of Canary 39.0.2149.0 Google Chrome 3 restore tabs.txt 759 KB
1 plugins Screen Shot 2014-09-07 at 4.53.47 PM.png 219 KB
2 play vid Screen Shot 2014-09-07 at 4.35.29 PM (2).png 1.1 MB
3 play video Screen Shot 2014-09-07 at 5.39.12 PM.png 112 KB
4 activity mon Screen Shot 2014-09-07 at 4.36.39 PM.png 103 KB
6 pause video Screen Shot 2014-09-07 at 5.33.58 PM.png 120 KB
7 close video tab Screen Shot 2014-09-07 at 5.36.17 PM.png 131 KB
8 restore a bunch of tabs Screen Shot 2014-09-07 at 5.59.04 PM.png 214 KB
10 restoring tabs Screen Shot 2014-09-07 at 5.57.44 PM.png 103 KB
11 restore a dozen tabs Screen Shot 2014-09-07 at 6.03.03 PM.png 67.0 KB
12 restore tabs cpu usage Screen Shot 2014-09-07 at 6.03.22 PM.png 102 KB