Closed
Bug 421703
Opened 16 years ago
Closed 15 years ago
Firefox leak during Smoketest with Firefox 3 Beta 4 RC2
Categories
(Core :: General, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Assigned: smaug)
References
()
Details
(Keywords: memory-leak)
Attachments
(2 files)
Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b4) Gecko/2008030714 Firefox/3.0b4 Was running the Smoketest in Litmus with the test to install a extension (adblock+ and W3v8 for Firefox) with a bunch of tabs open. This leak happened when i quit Firefox. Results of processing log leak2.log : Leaked outer window 1173ad0 at address 1173ad0. Leaked inner window 1173c80 (outer 1173ad0) at address 1173c80. ... with URI "about:blank". Leaked content nodes associated with node info manager at address 16e6840. Leaked content nodes associated with node info manager at address 1b98b40. Summary: Leaked 2 out of 118 DOM Windows Leaked 0 out of 146 documents Leaked 0 out of 40 docshells Leaked content nodes in 2 out of 159 documents Not sure if this is maybe something we fixed already on trunk.
Flags: blocking1.9?
Reporter | ||
Comment 1•16 years ago
|
||
Next leak log after the Extension and Theme was installed and firefox and after restart. Results of processing log leak3.log : Leaked outer window 211bcc0 at address 211bcc0. Leaked outer window 1219280 at address 1219280. Leaked inner window 1219430 (outer 1219280) at address 1219430. ... with URI "about:blank". Leaked content nodes associated with node info manager at address 238a3c0. Leaked content nodes associated with node info manager at address 1ae2d60. ... with document URI "http://www.heise.de/". Summary: Leaked 3 out of 105 DOM Windows Leaked 0 out of 112 documents Leaked 0 out of 35 docshells Leaked content nodes in 2 out of 122 documents
Comment 2•16 years ago
|
||
Tomcat talked with Jonas about this, will add more steps to reproduce, adding dbaron to cc to get his opinion.
Reporter | ||
Comment 3•16 years ago
|
||
For the Steps to reproduce (leak Comment#0) this leak happened while i was running the litmus smoketest testcases https://litmus.mozilla.org/show_test.cgi?searchType=by_category&product_id=1&branch_id=15&testgroup_id=54&subgroup_id=748 (without the extension/theme testcase). I will file a new bug for the leak report in comment #1
Reporter | ||
Comment 4•16 years ago
|
||
(In reply to comment #3) > I will file a new bug for the leak report in comment #1 > Note: thats now Bug 423336
Comment 5•16 years ago
|
||
Did dbaron have a chance to look at this leak log a bit more? Need to make a decision here on blocking.
Comment 6•16 years ago
|
||
I'm going to just go ahead and mark this as a P2 until we can get dbaron's advice. David's really busy right now, so, we'll have to wait a bit.
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2
Assignee | ||
Comment 7•16 years ago
|
||
I take this for now. Will look at this tomorrow (EET).
Assignee: nobody → Olli.Pettay
Assignee | ||
Comment 8•16 years ago
|
||
I went through those litmus tests, but XPCOM_MEM_LEAK_LOG didn't show any leaks. Tested also extension/theme installation separately. Is this something that XPCOM_MEM_LEAK_LOG doesn't show, but leak-gauge does. Tomcat, any chance to get exact steps-to-reproduce?
Reporter | ||
Comment 9•16 years ago
|
||
(In reply to comment #8) > Tomcat, any chance to get exact steps-to-reproduce? > Hm i just followed my steps to reproduce from http://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks:LeakTesting-How-To#Using_Leak_Gauge was not able to reproduce this leak with the RC2 of Firefox Beta 5, will renom or when i have solid steps to reproduce/testcase
Flags: blocking1.9+
Assignee | ||
Comment 10•15 years ago
|
||
Marking WFM. Tomcat, please reopen if you think this is still valid.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•