Open Bug 1453436 Opened 2 years ago Updated 6 months ago
Firefox is consuming 22 GB of Ram while using Dev Tools
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0 Build ID: 20180323154952 Steps to reproduce: I'm developing a React App, so I'm using the Dev Tools a lot. I don't 100% know the root cause of the memory leak, but it slows my developing time because I have to restart the system (due slow memory decompression and swap usage) twice or trice a day. I have less than 15 tabs open, and only on one I have the dev tools open. Actual results: I'm sharing the memory report, I don't fully understand it, the result is Huge Memory Usage, even under 12 tabs open. Expected results: I hope this is not the casual memory requirements for developing.
2 years ago
Component: Untriaged → Developer Tools
I don't know how to read memory reports, but I can see 219 instances of resource:\\\\devtools\\client\\debugger\\new\\parser-worker.js and 52 instances of resource:\\\\devtools\\client\\debugger\\new\\search-worker.js. Seems like an awful lot of them to me. In any case, 22GB is not normal. And having to restart Firefox either. It certainly seems like there's a leak somewhere. Do you see memory usage going up and up as you use Firefox? It could be good to also test using Firefox without addons (I'm assuming you're using the React DevTools addon at least), for some period of times, with DevTools open, and seeing if the leak persists there. This might be a similar bug as bug 1376753.
I fixed an issue in the debugger search worker that may be related to this issue. https://github.com/devtools-html/debugger.html/pull/7023 When searching the contents of a source using regular expressions that could return a zero length match such as /*a/ an inifiate loop would occur in the search worker that would keep adding to an array, causing several GB memory usage as well as high CPU usage. I think the fix has landed in the Nightly build.
Status: UNCONFIRMED → RESOLVED
Closed: 7 months ago
Resolution: --- → INACTIVE
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INACTIVE → ---
You need to log in before you can comment on or make changes to this bug.