On Tue, Jul 5, 2016, at 11:18 PM, Jed Davis wrote: > Benjamin Smedberg <benja...@smedbergs.us> writes: > > > Assuming these crashes show up in crash-stats.mozilla.com, are there > > particular signatures, metadata, or other patterns that would let us say > > "this crash is caused by a sandbox failure"? > > They should, and the expected distinguishing feature is a "Crash Reason" > of "SIGSYS". I put a certain amount of work into getting the crash > reporting integration to work properly back in the B2G era, and on > desktop for media plugin processes. (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 For example: https://dxr.mozilla.org/mozilla-central/source/browser/components/sessionstore/test/browser_crashedTabs.js 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. -Ted _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
