Memory leaking in browser process after opening DevTools |
|||||||||
Issue descriptionChrome Version: 49.0.2623.112 OS: Linux URL (if applicable) where the memory bloat occurred: any Can you reproduce this memory bloat? Yes What steps will reproduce this memory bloat (or if it's not reproducible, what were you doing until then)? (1) Open the Developer Tools once, and then the main Browser process starts accumulating ~1MB/s of private memory forever. This is 100% reproducible, and persists even if I close the Developer Tools, kill every other task and disable all extensions. The memory leak eventually grinds my entire machine to a halt.
,
Apr 13 2016
Obviously can't repro it. Did you try to run it with a clean profile, e.g. chrome --user-data-dir=/tmp/`date|md5sum` Also could you please record a trace at chrome://tracing having memory-infra category enabled.
,
Apr 13 2016
It does not happen with a clean profile. Tracing seems to be having troubles as well... I can successfully trace things before opening DevTools, but if I start a trace, open DevTools, then attempt to stop the trace, it hangs forever. The "stop" button goes gray, but nothing else happens.
,
Apr 13 2016
That's weird. Could you please open DevTools on DevTools (you have to have first DevTools undocked to do that) open the console there and execute: InspectorBackendClass.Options.dumpInspectorProtocolMessages = true to see if DevTools is running anything.
,
Apr 13 2016
I don't see anything appearing in the console other than my UI interactions
,
Apr 13 2016
Do you use workspaces in DevTools? If yes, could that be the workspace is too large? Try to remove the workspace.
,
Apr 14 2016
,
Apr 14 2016
Thank you for providing more feedback. Adding "Needs-Review" label for tracking. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 14 2016
That seems to have been the problem. I had added a folder at some point, but completely forgotten about it. I never would have solved it myself, so thank you! It does seem unfortunate, however, that this feature can have such negative effects on everything else
,
Apr 14 2016
Did it start leaking when you opened the devtools or after you tried searching? We only traverse fs upon opening, so it must be FileSystem API leaking. No wonder - the api is deprecated, we should migrate off it.
,
Apr 14 2016
It started immediately upon opening DevTools, even if I closed it without any interaction
,
Apr 29 2016
,
Jun 3 2016
,
Jul 7 2016
Was related to the ws. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by rnimmagadda@chromium.org
, Apr 13 2016