Closed
Bug 413263
Opened 16 years ago
Closed 7 years ago
Firefox leaks nsStringBuffer on https://dave.sni.velox.ch/
Categories
(Core :: General, defect, P4)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak)
Attachments
(1 file)
647 bytes,
text/plain
|
Details |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2008011516 Minefield/3.0b3pre Steps to reproduce: New Firefox Profile Go to https://dave.sni.velox.ch/ Create a Exception for this Site (Note, this might not work (crash) on Mac and Linux because of Bug 411743). After you have created the execption and you are able to surf this site, close Firefox Open Firefox and visit this site https://dave.sni.velox.ch/ - when you quit firefox, you get a leak report. This also works (leak) when you surf in later sessions to this site. 0 TOTAL 27 8 309526 1 ( 1149.00 +/- 1229.26) 941628 1 ( 1358.97 +/- 1933.09) 584 nsStringBuffer 8 8 22078 1 ( 3705.00 +/- 2009.01) 39378 1 ( 4250.70 +/- 2320.67)
Flags: blocking1.9?
Updated•16 years ago
|
Lowering priority, this leak is really small.
Priority: P2 → P4
Updated•16 years ago
|
Flags: tracking1.9+
This might have been fixed by my patch that stopped leaking nsHttpConnectionInfos.
Updated•16 years ago
|
Flags: wanted-next+
Comment 4•16 years ago
|
||
I got a bunch of leaks (including 2x nsGlobalWindow) when I tried following those steps :(
Comment 5•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
•