Closed
Bug 1340467
Opened 8 years ago
Closed 7 years ago
Debugger has a huge memory consumption
Categories
(DevTools :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jeremie.gourovitch, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170201180315
Steps to reproduce:
I'm developing for hours, doing nothing special but having an intense debugger usage, to debug JS/HTML/NETWORKS requests, lot of F5, etc..
Actual results:
I've 8go of RAM on my computer, it appears it's not sufficient to manage Firefox isage for a long time, i need hourly restart or the RAM usage increase dramatically...
There it is, even if i work on the same page, even if it doesn't need huge memory (for scripts by example), and with cache disabled, the RAM will be full filled with "unknown" data or what i call "junk-data"..
Expected results:
Some garbage collector system should have clean old pages, or old RAM area.
Ok, one more precision, i've obviously disabled my "persistant log".
Regards,
Updated•8 years ago
|
Component: Developer Tools: Debugger → Developer Tools: Framework
I think we'll need more memory details to better understand this.
Could you attach memory reports for this?
1. Go to about:memory before your debugging work
2. Click "measure and save" to save a "before" memory report
3. Proceed with debugging (whatever seems to trigger the memory issue)
4. Go to about:memory again
5. Click "measure and save" to save an "after" memory report
Attach these reports to the bug so that we can get a better idea of what's going on.
Blocks: dt-leak
Flags: needinfo?(jeremie.gourovitch)
Component: Developer Tools: Framework → Developer Tools
More data from the reporter is needed here. Please re-open if you're able to provide it.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jeremie.gourovitch)
Resolution: --- → INCOMPLETE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•