keeping devtools open leads to memory leak
Categories
(DevTools :: General, defect, P2)
Tracking
(Not tracked)
People
(Reporter: u619128, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(6 files, 1 obsolete file)
an image showing main process memory usage from my first replicate
steps to reproduce
- open an empty local html file using firefox.
- open console in this tab.
- write console.log("hi"), 1 + 2 and 3.5 + 3.5 in console.
- keep it open without interacting with it.
What happened?
main process kept increasing in size, it led my whole system being unresponsive.
the first time i replicate this the main process
Anything else we should know?
1- i was able to replicate this twice with a fresh profile.
2- i made four memory measurements one after starting firefox and reloading all tabs, one after (maybe) 7 hours, one after the previous measurement and after clicking on gc, cc and minimize memory buttons, the last one after closing devtools. note: all of these from the second replicate.
3- i don't get this problem when devtools aren't open even with the same webpages.
4- i don't know if this problem occurs with other devtools panels.
5- i rarely opened new tabs while using firefox and i made sure to close them before making a memory measurement(i closed one tab because i thought it caused this problem).
6- i found another bug while investigating this and i'm not sure if it's caused by this one, so i'm going to file it separately.
7- keeping firefox in the background doesn't change anything.
sorry for my mistakes, ignore the line "the first time i replicate this the main process" in What happened?.
i need to clarify something in "steps to reproduce", what i meant by "empty local html file" is this
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Document</title>
</head>
<body>
</body>
</html>
|
||
Comment 9•5 years ago
|
||
Hello rayan, thanks for the report
(In reply to rayan from comment #0)
steps to reproduce
- open an empty local html file using firefox.
- open console in this tab.
- write console.log("hi"), 1 + 2 and 3.5 + 3.5 in console.
- keep it open without interacting with it.
So here you're just loading the file and doing a few evaluation and that's it? you don't reload the page?
Was there other tabs open at the same time?
|
Reporter | |
Comment 10•5 years ago
|
||
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #9)
So here you're just loading the file and doing a few evaluation and that's it? you don't reload the page?
yes. I didn't reload it.
Was there other tabs open at the same time?
yes.
I'm doing more testing, i will come back to this later.
|
|
Reporter | |
Comment 11•5 years ago
|
||
i was able to replicate this in a different machine that has windows 10 with Firefox nightly(new profile) and I want to add some points:
1- reloading the page that has devtools doesn't free memory.
2- you don't need to open console or write anything, all you need is to keep devtools open.
3- to replicate this :
a. open some webpages like twitch.tv, wikipidia, reddit and mozilla.org.
b. open a simple html file like in comment 8.
c. open devtools in this tab.
d. keep reloading all tabs mentioned in the first step. (faster way to replicate)
e. see heap-unclassified increasing.
|
|
Reporter | |
Comment 12•4 years ago
|
||
while i was reading bugs that seem similar to this, i found this comment https://bugzilla.mozilla.org/show_bug.cgi?id=1565144#c17.
so i tried to test again by opening 10(https://www.mozilla.org/en-US/privacy/firefox/) tabs, then I opened the console from menu -> Web Developer -> Web Console in a local webpage(same as comment 8) without writing anything in console and kept reloading the 10 tabs for some amount of time until heap-unclassified reached 860MB.
then i tried things like memory minimize, keeping the browser in the background, keeping the browser in foreground without interacting with it, I even tried to close all tabs except the tab that has console with only seeing a tiny reduction maybe less than 20MB in heap-unclassified.
I also have done the same with style editor panel and got the same result.
|
||
Updated•2 years ago
|
Description
•