Firefox leaks with nsGlobalWindows when opening the Firefox Companion for Kodak EasyShare Extension Prefs

VERIFIED FIXED

Status

()

Core
General
P2
normal
VERIFIED FIXED
11 years ago
10 years ago

People

(Reporter: Tomcat, Unassigned)

Tracking

({memory-leak})

Trunk
x86
Windows XP
memory-leak
Points:
---
Dependency tree / graph
Bug Flags:
blocking1.9 +

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
Created attachment 296333 [details]
leak log

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
-> Install Firefox 2.x with the Firefox Companion for Kodak EasyShare Gallery https://addons.mozilla.org/en-US/firefox/addon/4441 and Nightly Tester Tool
-> Restart Firefox to make sure the extension is installed and Quit Firefox
-> Start the Firefox 3 Trunk Debug Build and make the Kodak Extension compatible with Firefox 3 (you can do this via tools-addons and the NTT button make compatible"
-> Restart Firefox - so far no leak
-> Click on the Options Button for this Extension in the Addon Manager 
-> Leak


nsTraceRefcntImpl::DumpStatistics: 767 entries
nsStringStats
 => mAllocCount:          30693
 => mReallocCount:         4369
 => mFreeCount:           30018  --  LEAKED 675 !!!
 => mShareCount:          33201
 => mAdoptCount:           3300
 => mAdoptFreeCount:       3293  --  LEAKED 7 !!!
Flags: blocking1.9?

Updated

11 years ago
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2

Updated

11 years ago
Depends on: 412136
(Reporter)

Comment 1

11 years ago
not leaking after the fix from bug 412491 went in and using Mozilla/5.0
(Windows; U;Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008012113
Minefield/3.0b3pre

-> Fixed (but i will retest this Firefox Companion when its relased for Firefox3).
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Reporter)

Comment 2

10 years ago
-> verified fixed
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.