759522 - OOM during mochitest-other

Status: RESOLVED DUPLICATE of bug 743396

(Core :: JavaScript Engine, defect)

Description

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Right now, when calling addDebuggee, we GC the compartment of the debuggee. This is great. However, during the devtools tests in mochitest-other, we do a ton of these GCs in a row. One problem with compartment GCs is that they clear the mark bits for compartments not being collected. That means that the cycle collector won't collect anything in those compartments.

So, in short, during a long span of time while running the devtools tests, we're not really able to collect anything with the cycle collector. We manage to squeak through these tests right now, although sometimes with only a few tens of megabytes of address space to spare. However, when I turn incremental GC on, it's a little slower to reclaim memory, and we often OOM during these tests.

The right way to fix this is to avoid clearing the mark bits during compartment GC. That's bug 743396. However, that could take some time. As a quick fix, it would be nice if we could do full GCs here. That would allow me to land incremental GC in FF15.

Comment 1

[Panos Astithas (he/him) [:past] (please ni?)]

Will sprinkling a few Components.utils.forceGC() or nsIDOMWindowUtils.garbageCollect() calls in the tests fix this? I could do that.

Comment 2

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Fixed this the right way.