Open
Bug 1020011
Opened 11 years ago
Updated 3 years ago
Segment::justify leaks |stats|
Categories
(Core :: Graphics: Text, defect)
Core
Graphics: Text
Tracking
()
NEW
People
(Reporter: mccr8, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: coverity, memory-leak)
This function allocates an array |stats|, and then as far as Coverity and I can see, just returns without freeing it.
![]() |
||
Comment 1•11 years ago
|
||
|stats| seems like a good candidate for stack allocation.
Comment 2•11 years ago
|
||
Ouch - yes, that looks like a bad leak. Fortunately, in Gecko we never call this at present. :) But cc'ing Martin so that upstream can fix it.
Comment 3•11 years ago
|
||
Thanks for spotting this. We will fix it. Is there any chance of getting the Graphite part of the coverity report so that we can address anything else it raises. We want Graphite to be as good code as we can make it. TIA.
Reporter | ||
Comment 4•11 years ago
|
||
(In reply to martin_hosken from comment #3)
> Thanks for spotting this. We will fix it. Is there any chance of getting the
> Graphite part of the coverity report so that we can address anything else it
> raises. We want Graphite to be as good code as we can make it. TIA.
Yeah, I can file bugs in bugzilla or email you about other things I see. Offhand, I didn't notice a ton of things in Graphite code.
Reporter | ||
Comment 5•11 years ago
|
||
I'm removing the MemShrink tag because we're not shipping this code in Firefox.
Whiteboard: [MemShrink]
Comment 6•9 years ago
|
||
fixed upstream
Updated•7 years ago
|
Blocks: coverity-analysis
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•