Issue metadata
Sign in to add a comment
|
Memory leak in Chrome main process when keeping navigating
Reported by
ypz...@gmail.com,
Mar 31 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: 1. Unpack the attached MemoryLeak.zip to get the simple demo extension. 2. Launch Chrome. 3. Load the unpacked extension. 4. Run for a period of time, for example, 30 minutes or 1 hour. 5. When running, open Windows performance monitor or other tools to monitor Chrome memory, especially Chrome main process memory. What is the expected behavior? No memory leak in Chrome main process. What went wrong? Memory leak in Chrome main process. Please see attached PNG files, which show the memory leak when running with the demo extension, for 1 hour. Three PNG file show private bytes, private working set, and working set memory. Did this work before? Yes I tested on Chrome 46, no memory leak in Chrome main process. Chrome version: 57.0.2987.110 Channel: stable OS Version: 6.3 Flash Version: The simple demo extension just keeps navigating to Google. Every 5 seconds, open a tab, navigate to Google, then close that tab. This is similar to normal user behaviors, keeping navigating. Notice in Chrome, when user navigates from URL A to URL B, the tab for URL A is closed, and a new tab is opened for URL B.
,
Mar 31 2017
Tested on Chrome 55, there is similar memory leak in Chrome main process.
,
Apr 4 2017
,
May 8 2017
benhenry@: could you triage? Seems to be related to tab manager.
,
May 8 2017
Kicking to another level of triage. This might be the same as crbug.com/718980 This bug has good traces and shows a reproducible memory leak with NTP.
,
May 16 2017
Issue 718980 is on Android, this one is on Windows, and they don't share the NTP implementation.
,
May 16 2017
+etienneb who is looking at NTP on desktop.
,
May 16 2017
,
May 17 2017
There is a bug for tab creation: https://bugs.chromium.org/p/chromium/issues/detail?id=707136 We recently landed a leak in mojo for every tab creation: https://bugs.chromium.org/p/chromium/issues/detail?id=704938 If this bug is still present on canary, I can give a look to it.
,
May 17 2017
There is a bug for tab creation [previous link was wrong]: https://bugs.chromium.org/p/chromium/issues/detail?id=705656 There is still this pending potential leak: https://bugs.chromium.org/p/chromium/issues/detail?id=707344
,
May 30 2017
This is probably related to this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=727830 We are seeing lot of Mojo objects leaked. see: https://docs.google.com/a/google.com/document/d/1ULZRYBElYmBDGswF3f4yYpl77SD9sa0RgFNfl1FueWU
,
Jun 5 2017
,
Jun 28 2017
,
Jul 26 2017
,
Sep 7 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ypz...@gmail.com
, Mar 31 2017