Closed
Bug 411609
Opened 17 years ago
Closed 17 years ago
Firefox leaks nsGlobalWindows when opening the "Nightly Tester Tools" Prefs
Categories
(Core :: General, defect, P2)
Tracking
()
VERIFIED
FIXED
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak)
Attachments
(1 file)
24.79 KB,
application/octet-stream
|
Details |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008010917 Minefield/3.0b3pre Steps to reproduce: -> New Firefox Profile -> Go to the Nightly Tester Tool Homepage http://www.oxymoronical.com/web/firefox/nightly -> Install the Extension -> Restart Firefox -> Use the Nightly Tester Tool -> so far no leak -> Go into the Addons Manager and click on the "Options" Button for this Extension -> Firefox leaks nsTraceRefcntImpl::DumpStatistics: 767 entries nsStringStats => mAllocCount: 25846 => mReallocCount: 4020 => mFreeCount: 25170 -- LEAKED 676 !!! => mShareCount: 25045 => mAdoptCount: 3009 => mAdoptFreeCount: 2995 -- LEAKED 14 !!!
Flags: blocking1.9?
Reporter | ||
Comment 1•17 years ago
|
||
jonas, peter: the steps to reproduce are similar to the steps from Bug 411593. Could it be that we have a general problem with leaks when extensions have this options button in the extension manager ?
Updated•17 years ago
|
Summary: Firefox leaks nsGlobalWindows when opening the Night Tester Tool Prefs → Firefox leaks nsGlobalWindows when opening the "Nightly Tester Tools" Prefs
Updated•17 years ago
|
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2
Comment 2•17 years ago
|
||
I've filed bug 412136 for a generic leak when opening the preferences for extensions from the add-ons manager. Seems like it hits a lot so it's unlikely to be extension specific.
Reporter | ||
Comment 3•17 years ago
|
||
not leaking after the fix from bug 412491 went in and using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre) Gecko/2008012105 Firefox/3.0b3pre -> Fixed
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•