794374 - Valgrind on tbpl detects leak - 3,520 bytes are definitely lost (direct) with nsComponentManagerImpl::ManifestComponent on the stack

Status: RESOLVED INCOMPLETE

(Core :: XPCOM, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Attachment: m-c changeset 08d435dedc7f Valgrind stack with line numbers

Valgrind detects a leak of 3,520 bytes (direct) with nsComponentManagerImpl::ManifestComponent 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.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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.

Comment 2

[Jens Stutte [:jstutte]]

I guess we would see these leaks with our current leak detection system, too.

Comment 3

[Andrew McCreight [:mccr8]]

We intentionally leak a lot of XPCOM component manager stuff for some reason. In leakcheck and LSan, we have ignore list stuff to deal with it. That said, I think it is fine to close this.