Closed
Bug 1000609
Opened 11 years ago
Closed 11 years ago
BlobSet does not free mData when it is destroyed
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla33
People
(Reporter: mccr8, Assigned: mccr8)
References
(Blocks 1 open bug)
Details
(Keywords: memory-leak, Whiteboard: [lsan][MemShrink:P2])
Attachments
(2 files)
3.40 KB,
text/plain
|
Details | |
889 bytes,
patch
|
khuey
:
review+
|
Details | Diff | Splinter Review |
Found while running crashtests under LSAN.
Assignee | ||
Updated•11 years ago
|
Whiteboard: [lsan] → [lsan][MemShrink]
![]() |
||
Updated•11 years ago
|
Whiteboard: [lsan][MemShrink] → [lsan][MemShrink:P2]
Assignee | ||
Comment 1•11 years ago
|
||
This leak is caused by
content/base/crashtests/xhr_abortinprogress.html
Assignee | ||
Comment 2•11 years ago
|
||
One way to fix the leak seems to be to add a dtor to BlobSet() that freed mData:
~BlobSet()
{
if (mData) {
free(mData);
}
}
What the test is doing is an XHR that is failing partway through, and so I guess the BlobSet just floats off into the ether somewhere. The actual BlobSet is being deleted somehow, but no flush or whatever occurs that frees the data.
Assignee | ||
Comment 3•11 years ago
|
||
The destruction of the BlobSet() is happening in nsXMLHttpRequest::ResetResponse(), which basically just deletes everything, so adding a dtor to BlobSet() seems like a reasonable approach.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → continuation
Assignee | ||
Updated•11 years ago
|
Summary: Leak in BlobSet::ExpandBufferSize → BlobSet does not free mData when it is destroyed
Assignee | ||
Comment 4•11 years ago
|
||
Attachment #8442405 -
Flags: review?(khuey)
Attachment #8442405 -
Flags: review?(khuey) → review+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Keywords: checkin-needed
Comment 6•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•