Closed
Bug 412039
Opened 17 years ago
Closed 16 years ago
Multiple leaks from using a few extensions
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: reed, Unassigned)
Details
(Keywords: memory-leak)
Attachments
(1 file)
|
29.10 KB,
text/plain
|
Details |
sayrer is helping me track down some leaks I'm seeing, so here's a XPCOM_MEM_LEAK_LOG for my profile. Not sure if these are extension problems or Gecko problems uncovered by extensions.
Active extensions:
Adblock Plus 0.7.5.3
DOM Inspector 1.9b3pre
Forecastfox 0.9.6
Nightly Tester Tools 1.3b1
Tinderstatus 0.2.8
See all the leaks I received from the following STR:
1. XPCOM_MEM_LEAK_LOG=leaklog-myprof-20080111.log ./firefox -no-remote -P
2. Select my profile and start browser
3. Browser opens with nothing saved from session restore
4. Select File->Quit and select "Quit"
5. Frown at leaks
Flags: blocking1.9?
| Reporter | ||
Updated•17 years ago
|
Attachment #296653 -
Attachment filename: leakmebabybe3.log → leaklog-myprof-20080111.log
Comment 1•17 years ago
|
||
I don't see any leaks when running with Adblock Plus 0.7.5.3, DOM Inspector 1.9b3pre and eMusic Remote Helper 1.0.0.2 (tried to do something in Adblock Plus, no changes). In general, Forecastfox would be the prime suspect when it comes to memory leaks. Can you check whether leaving only Forecastfox will produce the same memory leaks?
Comment 2•17 years ago
|
||
Reed can you retest and isolate the issue - if you get a good str re-nom
Flags: blocking1.9? → blocking1.9-
| Reporter | ||
Comment 3•16 years ago
|
||
Been almost two years since this bug was filed, so I'm going to close it out as INCOMPLETE for now, as I apparently never followed-up on the issue, and I don't have time to do so now.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•