Ted Mielczarek <t...@mielczarek.org> writes: > On Tue, Jul 5, 2016, at 11:18 PM, Jed Davis wrote: >> (However, there aren't automated >> tests to ensure it keeps working; "crashing the content process" isn't a >> use case that the test framework docs were very helpful with.) > > FYI, a number of mochitest-browser-chrome tests have since been written > that test crashing the content process: > https://dxr.mozilla.org/mozilla-central/search?q=path%3Abrowser_*crash&redirect=true
That would explain it -- originally only B2G could use any of this, and on B2G there was no browser-chrome, only mochitest-plain (and reftests). > There's even a BrowserTestUtils.crashBrowser function now: > https://dxr.mozilla.org/mozilla-central/rev/70e05c6832e831374604ac3ce7433971368dffe0/testing/mochitest/BrowserTestUtils/BrowserTestUtils.jsm#758 > > That just does a simple near-null deref using ctypes, but it could > easily be expanded to be more useful. Thanks for the pointers; filed bug 1285055. --Jed _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
