Closed
Bug 422270
Opened 16 years ago
Closed 7 years ago
Firefox leaks with the Yandex Toolbar installed
Categories
(Core :: General, defect, P2)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: cbook, Assigned: sicking)
References
Details
(Keywords: memory-leak, Whiteboard: [platform-rel-yandex])
Attachments
(3 files)
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b5pre) Gecko/2008031113 Firefox/3.0b5pre ID:2008031113 Steps to reproduce: - Install the Yandex Toolbar from http://bar.yandex.ru/firefox/ - Click around on this Toolbar, open some windows, options - Close Firefox --> Leak nsStringStats => mAllocCount: 55807 => mReallocCount: 7888 => mFreeCount: 54510 -- LEAKED 1297 !!! => mShareCount: 56098 => mAdoptCount: 4067 => mAdoptFreeCount: 4065 -- LEAKED 2 !!! 0 TOTAL 25 664743 1469899 19838 ( 3471.14 +/- 3790.17) 4035530 22865 ( 5066.94 +/- 7568.55)
Flags: blocking1.9?
Comment 1•16 years ago
|
||
+'ing w/ P2 as this is a very popular extension in Russia (like google toolbar).
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2
Assignee | ||
Comment 2•16 years ago
|
||
Tomcat, can you test this one to see if you can leak more than 2 nsGlobalWindows. If not we can fix this in a dot-release instead.
Comment 3•16 years ago
|
||
Need an owner, ASAP.
Assignee | ||
Comment 4•16 years ago
|
||
Tomcat, would be great to get better testing here. See comment 2. My list is getting short so I'll take this one.
Assignee: nobody → jonas
Reporter | ||
Comment 5•16 years ago
|
||
(In reply to comment #4) > Tomcat, would be great to get better testing here. See comment 2. > > My list is getting short so I'll take this one. > Hi Jonas, no 2 leaking Global Windows are the maximum i got leaking. So i think its okay to fix this for a dot release.
Assignee | ||
Comment 6•16 years ago
|
||
Excellent! Keeping a high priority since this is a very popular extension in some regions.
Flags: wanted1.9.0.x+
Flags: blocking1.9-
Flags: blocking1.9+
Comment 7•15 years ago
|
||
Leaked when "Cities (Weather)" elements removing. Fixed in 3.5.3+ (current version - 4.0.0).
Assignee | ||
Comment 8•15 years ago
|
||
Danil: It would be great to know what you were doing that caused firefox to leak. Most likely whatever you were doing should not have caused a leak and the leak was due to a bug in firefox. It's great that you have been able to work around the leak, but it'd also be great if we could fix the bug in firefox so that it doesn't appear again.
Comment 9•15 years ago
|
||
When the "city" item is being added to the toolbar, a pointer to this item is added to gYaCity hash. gYaCity is loaded by nsIYaSearch component (from chrome/content/sub-scripts/ya_city.js with mozIJSSubScriptLoader.loadSubScript). When the "city" item is being deleted, its' pointer is not deleted from those hash. A similar behaviour is shown by the component in attached script.
Comment 10•15 years ago
|
||
Yeah, components holding elements in global variables will leak. We've run into a bunch of these in frontend code, but no easy solution apart from changing the components code.
Updated•8 years ago
|
platform-rel: --- → ?
Updated•8 years ago
|
Whiteboard: [platform-rel-yandex]
Updated•7 years ago
|
platform-rel: ? → ---
Comment 11•7 years ago
|
||
Filter on QUANTUMLEAK
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•