Closed
Bug 794372
Opened 12 years ago
Closed 2 years ago
Valgrind on tbpl detects leak - 320 bytes are definitely lost (direct) with nsComponentManagerImpl::RegisterCIDEntry on the stack
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: gkw, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: memory-leak, valgrind)
Attachments
(2 files)
Valgrind detects a leak of 320 bytes (direct) with nsComponentManagerImpl::RegisterCIDEntry on the stack, see attached snippet which comes from:
https://tbpl.mozilla.org/php/getParsedLog.php?id=15521837&tree=Firefox&full=1
Guessing Core: XPCOM, please change component if necessary.
Reporter | ||
Comment 1•12 years ago
|
||
nsComponentManagerImpl::RegisterCIDEntryLocked is now appearing on another stack, which may be related.
Regression window: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b672877ed046&tochange=0f7261e288f2
Comment 2•2 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
Comment 3•2 years ago
|
||
I guess we would see these leaks with our current leak detection system, too.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•