1462702 - Add about pages in order to trigger a crash

Status: VERIFIED FIXED

(Core :: DOM: Core & HTML, enhancement, P3)

Description

[James Willcox (:snorp) ([e-mail]) (he/him)]

This is useful in order to test crash reporting or recovery in the case of a content process crash.

Comment 1

[James Willcox (:snorp) ([e-mail]) (he/him)]

Attachment: Bug 1462702 - Add about:crashparent and about:crashcontent

Review commit: https://reviewboard.mozilla.org/r/245146/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/245146/

Comment 2

[(no longer active)]

Comment on attachment 8977063 [details]
Bug 1462702 - Add about:crashparent and about:crashcontent

https://reviewboard.mozilla.org/r/245146/#review251198

::: docshell/base/nsAboutRedirector.cpp:140
(Diff revision 1)
>      nsIAboutModule::HIDE_FROM_ABOUTABOUT |
>      nsIAboutModule::URI_CAN_LOAD_IN_CHILD
> +  },
> +  {
> +    "crashparent", "about:blank",
> +    nsIAboutModule::URI_SAFE_FOR_UNTRUSTED_CONTENT

You probably want HIDE_FROM_ABOUTABOUT for both, so that this won't get listed in about:about.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d0034c0946ea
Add about:crashparent and about:crashcontent r=ehsan

Comment 4

[Eliza Balazs [:ebalazs_]]

https://hg.mozilla.org/mozilla-central/rev/d0034c0946ea

Comment 5

[Anca Soncutean, Desktop QA]

I successfully managed to use about:crashcontent (tab crash) and about:crashparent (browser crash) using a dirty profile on Firefox 62.0b8 (20180712042337) under Windows 10 x64, macOS 10.13 and Ubuntu 16.04 x64. The crashes generated this way are properly  logged and submitted to Socorro (verified them through about:crashes).

Comment 6

[Marcia Knous [:marcia]]

(In reply to Anca Soncutean [:Anca], Desktop Release QA from comment #5)
> I successfully managed to use about:crashcontent (tab crash) and
> about:crashparent (browser crash) using a dirty profile on Firefox 62.0b8
> (20180712042337) under Windows 10 x64, macOS 10.13 and Ubuntu 16.04 x64. The
> crashes generated this way are properly  logged and submitted to Socorro
> (verified them through about:crashes).

I think we should verify this on mobile as well, since I believe this was to help us verify crash reporting is working on Fennec.

Comment 7

[Anca Soncutean, Desktop QA]

Hi Ioana, 
Could someone from the mobile teem verify this implementation? Thank you!

Comment 8

[Bogdan Surd, QA [:bsurd, NI]]

Devices:
 - Samsung Galaxy S8 (Android 8);
 - Nexus 5 (Android 6.0.1);

Build:
 - Nightly (2018-07-17).

When using the about:crashparent the browser crashes and properly logs the crash in about:crashes. Nothing else is affected when restoring the session. (on the S8)

about:crashparent simply closes the app without prompting you to restart FF or logging a crash report (on the Nexus 5)

about:crashcontent displays a white page in comparison to the Desktop version of FF where you have the option to restore the tab. (for both devices)

Please NI me for any further details.