Chrome freeze in the morning |
|||||||||
Issue descriptionChrome Version : 67.0.3396.87 URLs (if applicable) : OS version : 10.13.5 (17F77) Behavior in Safari (if applicable): Not replicable Behavior in Firefox (if applicable): Not replicable What steps will reproduce the problem? (1) Configure your mac to never sleep, but to just turn the screen of. (2) Open Chrome, open a bunch of tab (3) Leave the office leaving the computer in that state (4) Come back after a long weekend, wakeup the screen, login (5) Chrome first beach ball (first sample, symbolicated) (6) Then Chrome is in a weird state where the UI is semi responsive (you can switch tab but not interact with content or close a tab) Second sample, also symbolicated. (7) Kill Chrome because you've been waiting for 5 minutes for it to recover, and it doesn't like it's going to happen anytime soon. What is the expected result? Chrome should be responsive the second the user logs in What happens instead? Chrome is frozen for minutes (I don't know how long, I never had the patience to wait) This is fully reproducible, just leaving the mac overnight reproduces the issue.
,
Jun 25 2018
If you haven't restarted Chrome since filing this report, please run: """vmmap -v -interleaved 557 > /tmp/chrome.vmmap" and upload the results. The real problem is a massive memory leak: """ Physical footprint: 19.4G Physical footprint (peak): 38.4G """ Maybe a dup of https://bugs.chromium.org/p/chromium/issues/detail?id=851506#c45. Maybe a different bug.
,
Jun 25 2018
,
Jun 26 2018
@Reporter: Could you please respond to comment# 2, hence adding Needs-Feedback label to it. Thanks!
,
Jun 26 2018
Sorry, I killed Chrome to get out of that state.
,
Jun 26 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 27 2018
@Reporter: Could you please try to test this issue on latest chrome stable# 67.0.3396.99 and let us know if the issue still persists. You can download chrome latest stable from URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
Jul 10
Issue still persist in 67.0.3396.99
,
Jul 10
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 10
This seem awfully similar to 849281.
,
Jul 11
@noyau - when you see this problem, please: 1) Run diagnostics from c#2 2) Run "heap -addresses=all -guessNonObjects <pid>"
,
Jul 12
A Gentle ping... @ noyau@chromium.org: Requesting you to please respond to comment #11. Adding Needs-Feedback label to it. Thanks..!
,
Jul 20
Assigning to noyau@ for followup.
,
Nov 23
***UI Mass Triage *** Adding labels for expert review.
,
Dec 17
Finally was able to catch Chrome locked up for long enough to run all the commands ❯❯❯ sudo vmmap -v -interleaved 46857 > /tmp/chrome.vmmap ❯❯❯ sudo heap -addresses=all -guessNonObjects 46857 > /tmp/chrome.heap I was never able to get enough time to run those commands before as Chrome was not locking for long enough. I'm running into issues attaching the files (they are big!) (This is Chrome 70.0.3538.110)
,
Dec 17
,
Dec 17
The heap file is too big. Stored it on drive, compressed instead of this bug. https://drive.google.com/open?id=1M94wwc3ZhuwMQO9rKsyMPk_pHSan47zz
,
Dec 17
From vmmap: """ 23814 MALLOC ZONE SIZE SIZE SIZE SIZE COUNT ALLOCATED FRAG SIZE % FRAG COUNT 23815 =========== ======= ========= ========= ========= ========= ========= ========= ====== ====== 23816 DefaultMallocZone_0x10cbbe000 31.2G 18.8G 14.1G 8.7G 95448303 20.4G 2.4G 11% 21150 23817 QuartzCore_0x12375d000 112.0M 1000K 960K 104K 4418 283K 781K 74% 35 23818 WebKit Malloc_0x7fffaac47398 3072K 0K 0K 244K 3 3072K 0K 0% 3 23819 x-alloc_0x7fbb50286800 8K 8K 8K 0K 19 304 8K 97% 2 23820 DefaultPurgeableMallocZone_0x10cc4c000 4K 4K 4K 0K 0 0K 4K 100% 1 23821 GFXMallocZone_0x10cbe5000 0K 0K 0K 0K 0 0K 0K 0% 0 23822 =========== ======= ========= ========= ========= ========= ========= ========= ====== ====== 23823 TOTAL 31.3G 18.8G 14.1G 8.7G 95452743 20.4G 2.4G 11% 21191 """ malloc is going crazy. Hopefully we can symbolize the heap file to figure out the root problem.
,
Dec 17
Err, in this case, the heap isn't useful -- all it shows is that there's a lot of malloc allocations. :( Let's try this: Go to chrome://flags and turn on #memlog=browser, #memlog-sampling=enabled. This will enable super-low overhead heap profiling. When you experienced this problem, Chrome is unusable, but eventually becomes usable, right? After it becomes usable, go to chrome://memory-internals and save a heap dump. Hopefully, whatever problem you're experiencing will still leave behind a lot of artifacts in the heap that we can use to figure out the root cause.
,
Dec 26
This is systematic if I don't touch my desktop for a few days. Unfortunately, leaving it for a week-end is not enough, if recovers too fast for me to grab the data. It happened again this morning, but of course I had not seen your comment, sorry. I also had killed the browser as it was taking way too long to recover. Anyway, I got another capture and attached it, not sure it's going to be of any use. The file is again too big to store in the bug, I put it in drive: https://drive.google.com/open?id=1IIng8hnJB_PHLtyAJqEoRUWRmkqB8RFP I turned the requested flags on, hopefully the issue will reproduce over the long new year week end. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by lgrey@chromium.org
, Jun 25 2018Components: UI>Browser