937726 - Investigate ASan OOMs for devtools tests

Status: RESOLVED DUPLICATE of bug 938310

(DevTools :: General, defect)

Description

[Shu-yu Guo [:shu]]

Bug 933882 turns off the massive GC that gets forced every debug mode toggle, but this has caused ASan builds to OOM; see https://bugzilla.mozilla.org/show_bug.cgi?id=933882#c16

I've papered over this by forcing GC from the Debugger test harness instead, but we should figure out if we're in fact doing something wrong in the tests to cause OOMs.

That said, ASan browser-chrome plain uses a lot of memory. I have half a mind to blame this on infra: Why aren't we running ASan builds on slaves with more memory? Why can't we modify the memory pressure triggers to be aware of ASan (I'm told b2g builds can get memory pressure triggers from the kernel)? Why are tests run consecutively in one instance of Firefox, so that any leaks from earlier tests will accumulate in later tests?

Comment 1

[Phil Ringnalda (:philor)]

It wasn't actually ASan only, that was just the clearest and most consistent thing to fail. There were also timeouts and CC assertions about OOM in the same test on non-ASan builds.