Re: Crash reports with Fission enabled are now indicated by DOMFissionEnabled = 1

2019-07-05 Thread Andrew McCreight
On Fri, Jul 5, 2019 at 7:50 PM Masatoshi Kimura wrote: > On 2019/07/06 6:54, Andrew McCreight wrote: > >> Here's an example of a crash report with DOMFissionEnabled: > >> > https://crash-stats.mozilla.org/report/index/dac0a91a-ad57-4446-9a82-505a80190705#tab-metadata > > I could not find `DOMFiss

Re: Crash reports with Fission enabled are now indicated by DOMFissionEnabled = 1

2019-07-05 Thread Masatoshi Kimura
On 2019/07/06 6:54, Andrew McCreight wrote: >> Here's an example of a crash report with DOMFissionEnabled: >> https://crash-stats.mozilla.org/report/index/dac0a91a-ad57-4446-9a82-505a80190705#tab-metadata I could not find `DOMFissionEnabled` in this crash report (although `DOMIPCEnabled` is found)

Re: Crash reports with Fission enabled are now indicated by DOMFissionEnabled = 1

2019-07-05 Thread Andrew McCreight
On Fri, Jul 5, 2019 at 1:12 PM Andrew McCreight wrote: > I landed bug 1560977 a few days ago, so you can now see in a crash report > if Fission was enabled. If it was, the "meta data" tab will have a value of > 1 for DOMFissionEnabled. The behavior is modeled after DOMIPCEnabled which > indicates