Bug 1666383 Comment 14 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I tried to verify this fix, unsuccessfully.

First off, the fix seems to be about content process crashes, not parent process crashes. Of the five crash reports in comment 0 and comment 1, only two reports were from a content process crash (the two "Here are two more" reports). The other three are from parent process crashes.

 So I navigated to `about:crashcontent` in Firefox Nightly. Here's the report I got: https://crash-stats.mozilla.org/report/index/fc1c7397-20e6-42c8-a071-702e80201210
It does not have a "moz crash reason" field. So it looks like the fix didn't fix the bug on my phone. The build I used definitely includes the patch from this bug.

Then I tried to see if I at least got a moz crash reason from `about:crashparent`. However, `about:crashparent` doesn't even generate a crash report anymore. I filed that as https://github.com/mozilla-mobile/android-components/issues/9195 .
I tried to verify this fix, unsuccessfully.

First off, the fix seems to be about content process crashes, not parent process crashes. Of the five crash reports in comment 0 and comment 1, only two reports were from a content process crash (the two "Here are two more" reports). The other three are from parent process crashes.

 So I navigated to `about:crashcontent` in Firefox Nightly. Here's the report I got: https://crash-stats.mozilla.org/report/index/fc1c7397-20e6-42c8-a071-702e80201210
It does not have a "moz crash reason" field. So it looks like the fix didn't fix the bug on my phone. The build I used definitely includes the patch from this bug.

Then I tried to see if I at least got a moz crash reason from `about:crashparent`. However, `about:crashparent` doesn't even generate a crash report anymore. I filed that as bug 1681842.

Back to Bug 1666383 Comment 14