Categories
(Core :: Graphics: ImageLib, defect)
Core
Graphics: ImageLib
Tracking
()
VERIFIED
WONTFIX
mozilla0.9
People
(Reporter: bratell, Assigned: saari)
Details
(Keywords: memory-leak, Whiteboard: [libpr0n][tind-mlk])
The fix for bug 61756 caused a (or several) memory leaks, which was directly visble on tinderbox. The fix was a one liner that returned early which seemed to have jumped some cleaning up. I guess this is a dupe, but I couldn't find another bug.
Whiteboard: [tind-mlk]
Reporter | ||
Comment 1•24 years ago
|
||
According to tinderbox, the following started to leak: ImgDCallbk 144 - ImageNetContextImpl 288 - ImageRendererImpl 12 - nsVoidArray 72 -
Comment 3•24 years ago
|
||
saari, would be great if we could get this for .8 (within the next few days)
Keywords: mozilla0.8
Assignee | ||
Comment 4•24 years ago
|
||
The leak is timing releated, and of course, when I do hit the new one line of code, I always see things cleaned up properly later, probably because I'm changing the timing. Anyone know what speed the leak test machine is?
Comment 5•24 years ago
|
||
the code causing this bug is going away, and us wasting time trying to fix this is only going to delay us replacing this code. I don't see any reason to continue work on this bug.
Assignee | ||
Comment 6•24 years ago
|
||
I thought I had a fix for this but discovered that I really don't understand the current imglib ownership model and my fix was totoally ineffective. Rather than spend more time on this I'm focusing on the new code, bug leaving this bug open until that new code lands.
Status: NEW → ASSIGNED
Assignee | ||
Comment 7•24 years ago
|
||
will be "fixed" by libpr0n. The leak is in old, end of life code.
Whiteboard: [tind-mlk] → [libpr0n][tind-mlk]
Target Milestone: --- → mozilla0.9
Updated•24 years ago
|
Keywords: mozilla0.8.1
Updated•24 years ago
|
Keywords: mozilla0.8
Assignee | ||
Comment 8•23 years ago
|
||
libpr0n is on, this is now dead
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•