Closed Bug 1373340 Opened 7 years ago Closed 6 years ago

Intermittent LeakSanitizer | leak at Malloc, nsTArray_base, AppendElements, IPC::ParamTraits

Categories

(Core :: IPC, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: intermittent-failure, memory-leak, Whiteboard: [MemShrink:P3])

Keywords: mlk
We're leaking a single large array, under mozilla::loader::PScriptCacheParent::Read.
Blocks: 933741
Flags: needinfo?(kmaglione+bmo)
It looks like this is the xdrData field of ScriptData.
Whiteboard: [MemShrink]
Hm. I guess that means there's a problem with the move semantics when we process that array, but I'm surprised that it would only be intermittent if that's the case.
Flags: needinfo?(kmaglione+bmo)
Yeah, it is quite strange. Normally I'd imagine that we drop the array in some error case, but this looks associated with an nsTArray, not a raw C array, so I don't know how that would happen.
Kris have you had a chance to look at this further? It seem like a rather large leak put pretty rare.
Flags: needinfo?(kmaglione+bmo)
I've looked into it a few times, but haven't been able to come up with any plausible way for this to leak.

The only possibilities I can think of are broken move semantics (which doesn't seem to be the case), or the mXDRData MaybeOneOf somehow getting re-constructed after the array is moved to it (which, from my reading of the code, shouldn't be possible).

Since this seems to only have ever happened once, I'm not sure how much more time it's worth spending on it.
Flags: needinfo?(kmaglione+bmo)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [MemShrink] → [MemShrink:P3]
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Priority: -- → P3
Status: REOPENED → RESOLVED
Closed: 7 years ago6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.