Memory consumption continually increases and browser becomes unstable |
|||||||||
Issue descriptionVersion 58.0.3029.81 OS: Win7-64 Can you reproduce this memory bloat? Yes. Just starting the browser causes it. What steps will reproduce this memory bloat: Launch browser. Once the largest of the many chrome.exe *32 processes has over 3.1GB of Private Working Set memory, it becomes unstable. It frequency crashes on animated GIFs in email signatures, with an odd delay of about 13 seconds after the GIF is displayed. Additionally, some web pages will fail unexpectedly. Watching the memory usage in Task Manager, I see it continually going up. 240.5MB at 11:44 on 5/2.
,
May 2 2017
,
May 2 2017
Of the processes below, the following ones show constant activity, but it's not clear that they're ascending: - the two calendar entries, but the highlighted one at a faster rate - the two inbox entries The one on @google email seems to be relatively monotonic and increasing slowly I tried the memory trace, but it crashes: Tim Prachar | Google Hardware -- Sensors | tprachar@google.com | 650-762-6497
,
May 3 2017
Note the climb from yesterday: Tim Prachar | Google Hardware -- Sensors | tprachar@google.com | 650-762-6497
,
May 8 2017
And continues to grow: Tim Prachar | Google Hardware -- Sensors | tprachar@google.com | 650-762-6497
,
May 10 2017
And continues: Tim Prachar | Google Hardware -- Sensors | tprachar@google.com | 650-762-6497
,
May 12 2017
,
May 12 2017
The memory consumption has continued to increase unabated. At this level typing is impaired. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Keyboard input is ignored for 2-3 seconds ever few seconds, making composition nearly impossible. Tim Prachar | Google Hardware -- Sensors | tprachar@google.com | 650-762-6497
,
May 30 2017
tprachar: Could you try to grab a memory trace as per comment 1? Thanks.
,
May 30 2017
Please read my comments about the memory trace on May 2nd in response to the original request. Tim Prachar | Google Hardware -- Sensors | tprachar@google.com | 650-762-6497
,
May 30 2017
Thank you for providing more feedback. Adding requester "grt@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 20 2017
Tim, we cannot see your images as they do not upload when you reply to these bugs via email. Can you please attach a trace .json output to the actual bug? +jrobbins to see if there's anything we can do about that.
,
Jun 20 2017
How do I get the "trace.json"? If that's the output of the memory trace, it's not possible as memory trace crashes. Tim Prachar | Google Hardware -- Sensors | tprachar@google.com | 650-762-6497
,
Jul 18 2017
,
Sep 20 2017
,
Feb 22 2018
There have been many memory fixes since May 2017. If this continues to occur, feel free to reopen. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by rsch...@chromium.org
, May 2 2017