1961331 - Paired minidumps are likely mishandled by the Android crash reporter

Status: NEW

(Firefox for Android :: Crash Reporting, defect)

Description

[Gabriele Svelto [:gsvelto]]

While digging through crash pings me and :gcp noticed some odd crashes popping up. Chasing them down to Socorro I found crashes like this one which have a number of peculiar characteristics:

• It ostensibly appears to be a main-process crash, but if you look at the threads you'll quickly notice that it's really coming from a GPU process
• It is missing all the native crash annotations, having instead only those that are added to the crash report by the Java code
• It is not a real crash as the reason is DUMP_REQUESTED which can only happen when the main process takes a snapshot of a non-crashed child process

I traced down the code generation this crash here where we take a minidump of both the main process and the GPU process before crashing. The resulting crash report will look like this:

• An <uuid>.extra with the native crash annotations, and among them the additional_minidumps annotation containing only the entry browser
• An <uuid>.dmp file holding the minidump of the GPU process
• An <uuid>-browser.dmp file holding the minidump of the main process

This should be submitted as a single crash report, see the code here for how we do it in desktop Firefox. What is likely happening right now is that the dumps are being submitted independently and are possibly missing the .extra file entirely.

Comment 1

[Alex Franchuk [:afranchuk]]

Does this occur in a "normal" main process crash (where we have to display the crash reporter client)? If so, the client also doesn't handle this case.

Comment 2

[Gabriele Svelto [:gsvelto]]

No, this only happens in case of IPC failures where the main process kills a child process but also takes a dump of itself before doing so, see here.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:royang, could you have a look please?

For more information, please visit BugBot documentation.