Closed Bug 443675 Opened 17 years ago Closed 8 years ago

Firefox leaks 35 (and more) nsGlobalWindows when the Webvisium Extension is used

Categories

(Core :: General, defect)

1.9.0 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak)

Attachments

(2 files)

Attached file leak log
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008070118 Minefield/3.0.1pre + new Debug Build on Linux Fedora 9 Steps to reproduce: -> Install the Webvisum Extension (from http://www.webvisum.com/en/main/download) and login (you need to register a Account) -> Start Firefox with this Extension installed -> Go to few sites, as example login into your Gmail Account -> Close Firefox --> Leak Note: Marco blogged about this Extension (http://www.marcozehe.de/2008/07/03/review-of-the-webvisum-firefox-extension/) and so it might become a popular Extension for our Accessibility Community/User Also i was able to get 40 leaking nsGlobal Windows in a second test...so this leak is building up :/ nsStringStats => mAllocCount: 56221 => mReallocCount: 7946 => mFreeCount: 48215 -- LEAKED 8006 !!! => mShareCount: 63041 => mAdoptCount: 5800 => mAdoptFreeCount: 5784 -- LEAKED 16 !!! 0 TOTAL 26 2540577 3429657 95759 (14576.28 +/- 11671.07) 4760173 64907 ( 4338.57 +/- 6731.43)
Flags: blocking1.9.1?
Flags: blocking1.9.0.2?
i have done a test with a lot of tabs (around 100 tabs with popular sites like gmail, yahoo mail etc) and running Firefox with this Extension over about 18 hours.. And i leak 461! nsGlobal Windows 430 nsGlobalWindow 428 197308 634 461 ( 278.39 +/- 167.20) 63124289 922 ( 1614.07 +/- 166.85) Result: nsStringStats => mAllocCount: 15420158 => mReallocCount: 1154440 => mFreeCount: 15329159 -- LEAKED 90999 !!! => mShareCount: 13989210 => mAdoptCount: 132361 => mAdoptFreeCount: 132334 -- LEAKED 27 !!! 0 TOTAL 1 33917064 -903056003 1264266 (596405.93 +/- 0.00) 1992334695 1110920 (41604.38 +/- 0.00)
We really should have the extension developers look at this and see if there's anything they can do on their end.
Chatting with Tomcat on IRC he mentioned that you, sicking, suggested we run the extension with various parts disabled to find what the leaky area is (a la binary search). We do not have a debug build of Firefox and we're unable to produce the leak report Tomcat showed when he opened the bug. Even though we develop the extension, I don't know if we're the right people to address the problem as we're lacking the tools, and possibly knowledge, to do so. Let us know how we can help. You're most welcome to download and give the extension a try from www.webvisum.com - tomcat mentioned that he simply installed it and went to his googlemail account to produce the report above. Thanks
Not blocking, but wanted if it's something on our end.
Flags: wanted1.9.0.x+
Flags: blocking1.9.0.2?
Flags: blocking1.9.0.2-
blocking1.9.1-=damons
Flags: blocking1.9.1? → blocking1.9.1-
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: