Closed Bug 432154 Opened 16 years ago Closed 7 years ago

Firefox leaks when uninstalling the Biotech Extension

Categories

(Core :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak)

Attachments

(1 file)

Attached file leak log
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9pre) Gecko/2008050221 Firefox/3.0pre

Steps to reproduce:
-> Install the Biotech Extension
-> Open the Sidebar (click on some buttons, etc)
-> Close Firefox (this should not leak here)
-> Uninstall this Extension in the next session
--> Leaks

nsStringStats
 => mAllocCount:          35049
 => mReallocCount:         5273
 => mFreeCount:           33778  --  LEAKED 1271 !!!
 => mShareCount:          31612
 => mAdoptCount:           2916
 => mAdoptFreeCount:       2914  --  LEAKED 2 !!!

   0 TOTAL                                          26   355923   790935    11708 ( 2393.09 +/-  2315.05)  2431033     7178 ( 3411.44 +/-  5235.74)
Blocks: 432156
Blocks: 432157
Blocks: 432326
Blocks: 432640
Blocks: 432688
Blocks: 433360
Flags: wanted1.9.0.x?
Flags: blocking1.9.0.1?
Blocks: 437121
Blocks: 437122
Blocks: 437146, 437147
Blocks: 437148
Blocks: 437149
Blocks: 438357
Blocks: 438454
Blocks: 438458
Blocks: 438459
Blocks: 438846
Blocks: 438847
Blocks: 438849
Blocks: 438973
Blocks: 438976
Blocks: 438977
Blocks: 439135
Blocks: 439136, 439137
Blocks: 441645
Flags: blocking1.9.0.1? → blocking1.9.0.1-
You seem to have filed a lot of bug reports of this form; it seems like they're likely to have a common cause.  (I tried testing bug 432157 and couldn't reproduce it.)

(In reply to comment #0)
> -> Install the Biotech Extension
> -> Open the Sidebar (click on some buttons, etc)

Is this necessary?  If so, what are the minimal steps necessary?

> -> Close Firefox (this should not leak here)
> -> Uninstall this Extension in the next session
> --> Leaks

Do you choose "restart firefox" when you uninstall?  Either way, is this bug reporting leaks in the instance before the restart or the instance after the restart?  I didn't see leaks in either.
(In reply to comment #1)
> Is this necessary?  If so, what are the minimal steps necessary?
> 
No, thats not necessary, i only do this to verify that the extension is working. 
> 
> Do you choose "restart firefox" when you uninstall?  Either way, is this bug
> reporting leaks in the instance before the restart or the instance after the
> restart?  I didn't see leaks in either.

No, i close Firefox manually to check the logfile, with "restart firefox", the Memory Leak Logging to the Logfile would be overwritten when Firefox restarts, so i choose the manual variant

> I didn't see leaks in either.

I will do some restart in the next days
would be nice for 1.9.0.x, but we'll look at it after a trunk fix.
Flags: wanted1.9.0.x?
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.

Attachment

General

Created:
Updated:
Size: