Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
Tracks the current rank of this item in the teams backlog [ID: 1225362]
Build number, such as 117.0.5911.2 [ID: 1223033]
Remove item
[ID: 1223031]
Internals>GPU
Select items in the list
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
he CWE ID for the type of security defect the current issue is describing. [ID: 1410892]
Design doc to be reviewed. [ID: 1223032]
[ID: 1223131]
How many engineer days the task is estimated to take. [ID: 1225337]
[ID: 1223081]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
Date of next expected progress update or deadline for providing requested information. [ID: 1225154]
[ID: 1223083]
[ID: 1223084]
[ID: 1223086]
[ID: 1223034]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223088]
[ID: 1223135]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Internals
[ID: 1253656]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Estimated effort
Description
#1Steps to reproduce the problem:
1. Start Chrome, open lots of tabs
2. Put computer to sleep
3. Wake from sleep
What is the expected behavior?
All tabs should respond promptly upon wake from sleep
What went wrong?
After wake from sleep, Chrome is unresponsive. Tabs don't respond. This behaviour can last from a couple of minutes up to a point when I just restart the browser. Sometimes it "heals" itsself, sometimes it does not.
In the task manager, the Chrome process itsself is using between 50 and 80% CPU time. This never happens in normal operation.
I have my Chrome tabs spread out over several windows and desktops.
Sometimes just switching between those windows will "heal" the browser.
Sometimes it won't. In case it heals itsself, CPU usage quickly drops down to
below 10%.
Using dtruss and sc_usage I was able to see that the Chrome process makes thousands and thousands of calls to kevent() during this period, like so:
kevent(0x1D, 0x7A2C6000, 0x0) = 0 0
kevent(0x1D, 0x7A2C6000, 0x0) = 0 0
kevent(0x1D, 0x7A2C6000, 0x0) = 1 0
Unfortunately, I have no idea what it is trying to do here. :-(
This issue seems to be not so infrequent, I could find several postings reporting similar behaviour, like here in
I tried creating a new profile already, but without much success. Now I'm really out of ideas what to try next.
Did this work before? Yes MacOS 10.6.x Snow Leopard
Chrome version: 27.0.1453.81 Channel: beta
OS Version: OS X 10.8.3
HELP ;-)