1441052 - Don't do full grey-node checking in local debug builds

Status: NEW

(Core :: JavaScript: GC, enhancement, P3)

Description

[Randell Jesup [:jesup] (needinfo me)]

Debug builds have assertions that would catch many problems if used for regular browsing -- but they are *far* too slow to use for browsing.  We have a grey-node check inside MOZ_ASSERT, ifdef'd off for android as it makes everything fail there because it's even slower in emulation.

This is bad, because it makes it hard-to-impossible for developers to regularly run debug builds (and thus they miss catching bugs as early as they could).  I used to do most of my basic webrtc testing in debug builds, but it became too slow to get calls to reliably connect on services like appear.in.

For local (developer) debug builds, we should turn off this extra checking by default.  We can continue to use it in automation.  We could also consider if there's a lower-overhead set of tests we could do, or tests that don't impact mainthread as harshly (perhaps there is no such option, though).