Closed
Bug 793548
Opened 12 years ago
Closed 11 years ago
Valgrind on tbpl detects leak at malloc (72 bytes in 1 blocks are definitely lost) with CrashReporter::SetupExtraData on the stack
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gkw, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: memory-leak, valgrind)
Attachments
(1 file, 1 obsolete file)
(deleted),
text/plain
|
Details |
Valgrind detects a leak of 72 bytes at malloc with CrashReporter::SetupExtraData on the stack, see attached snippet which comes from:
https://tbpl.mozilla.org/php/getParsedLog.php?id=15458553&tree=Firefox&full=1
Reporter | ||
Comment 1•12 years ago
|
||
Guessing Core:XPCOM, please change component if necessary.
Updated•12 years ago
|
Component: XPCOM → Breakpad Integration
Product: Core → Toolkit
Reporter | ||
Updated•12 years ago
|
Blocks: valgrind-tbpl-bugs
Reporter | ||
Updated•12 years ago
|
No longer blocks: valgrind-on-tbpl
Reporter | ||
Comment 2•12 years ago
|
||
Attachment #663873 -
Attachment is obsolete: true
Reporter | ||
Comment 3•12 years ago
|
||
Suppression updated in https://hg.mozilla.org/mozilla-central/rev/766f39da353b
Comment 4•11 years ago
|
||
This is another one where we deliberately leak due to the use of PR_SetEnv(). The suppression (already present) is the right way to handle it.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•