1852039 - Various base.odex crashes on Android

Status: RESOLVED FIXED

(Toolkit :: Crash Reporting, defect)

Description

[Donal Meehan [:dmeehan]]

Crash report: https://crash-stats.mozilla.org/report/index/1e88dac8-0a44-4cfe-bd0a-338300230907

Reports started from Fenix build ID 20230901154021

MOZ_CRASH Reason: MOZ_CRASH(DocumentChannel::SetLoadFlags: Don't set flags after creation)

Top 10 frames of crashing thread:

0  ?  @0x0000007c2ba190dc  
1  ?  @0x0000007c2e8410b0  
2  ?  @0x0000007c2ba19748  
3  ?  @0x0000007c2bbae12c  
4  ?  @0x0000007c2dbc3878  
5  ?  @0x0000007c2eeedbfc  
6  ?  @0x0000007c2dbec8f0  
7  ?  @0x0000007c2e41d524  
8  ?  @0x0000007c2e7fa864  
9  ?  @0x0000007c2e41e558  

Comment 1

[Donal Meehan [:dmeehan]]

:jonalmeida tracking this crash due to the volume in nightly, not sure what introduced it.
As triage owner, could you follow up on a severity/investigation?

Comment 2

[Jonathan Almeida [:jonalmeida]]

I don't see anything here that pertains to Fenix, Android Components, or GeckoView code.

Could someone in necko have a closer look and advise?

Comment 3

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

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 10 AArch64 and ARM crashes on nightly

For more information, please visit BugBot documentation.

Comment 4

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

The bug is marked as tracked for firefox119 (nightly). We have limited time to fix this, the soft freeze is in 13 days. However, the bug still isn't assigned.

:ghess, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Comment 5

[Kershaw Chang [:kershaw]]

This is a dup.

Comment 6

[Andrew McCreight [:mccr8]]

gsvelto, do you know what is going on with these base.odex crashes? Fenix only. It looks like they've been going on for awhile. I'll reopen this and move it to crash reporting.

Comment 7

[Gian-Carlo Pascutto [:gcp]]

Crash Ping Telemetry indicates a 6x fold increase of content process crashes on Fenix. We don't get stacks yet but this could be the relevant signature for it.

Comment 8

[Gian-Carlo Pascutto [:gcp]]

There's also some MOZ_DIAGNOSTIC_ASSERT(false) (Setting DocumentURI with a different origin than principal URI)

Comment 9

[Andrew McCreight [:mccr8]]

(In reply to Gian-Carlo Pascutto [:gcp] from comment #8)

There's also some MOZ_DIAGNOSTIC_ASSERT(false) (Setting DocumentURI with a different origin than principal URI)

That one is for an issue that got backed out at least. These crashes kind of look like a random grab bag of Android issues, which is why I thought it might be some kind of crash reporting issue.

Comment 10

[Gabriele Svelto [:gsvelto]]

This is caused by bug 1837471 which is a bug in the minidump writer, I'll have to prioritize fixing it.

Comment 11

[Gian-Carlo Pascutto [:gcp]]

That one is for an issue that got backed out at least.

Do you have the link? Our crash Telemetry doesn't have stacks yet, but maybe build numbers give a clue.

Comment 12

[Andrew McCreight [:mccr8]]

(In reply to Gian-Carlo Pascutto [:gcp] from comment #11)

Do you have the link? Our crash Telemetry doesn't have stacks yet, but maybe build numbers give a clue.

Bug 1783504. (and see also bug 1852227)

Comment 13

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

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox119 (nightly). We have limited time to fix this, the soft freeze is in 7 days. However, the bug still isn't assigned.

Comment 14

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

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox119 (nightly). We have limited time to fix this, the soft freeze is in a day. However, the bug still isn't assigned.

Comment 15

[Gabriele Svelto [:gsvelto]]

With bug 1837471 fixed the volume here should start dropping. I'm going to wait a couple of days to see the effect in nightly then I'll request to uplift the fix in beta. Note that the overall crash volume of Fenix won't change, as the crashes under this bug are really other valid crashes (such as bug 1694904) so the volume will move under those bugs.

I've filed some bugs based on the other hidden crashes here. One is bug 1855400 where the Android volume ended up here, another one is bug 1800558 which will see its volume raise rapidly.

Comment 16

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

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit BugBot documentation.

Comment 17

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

This is a reminder regarding comment #4!

The bug is marked as tracked for firefox119 (beta). We have limited time to fix this, the soft freeze is in 14 days. However, the bug still isn't assigned.

Comment 18

[Donal Meehan [:dmeehan]]

Removing tracking, bug 1837471 was uplifted to beta for Fx119 (see comment 15)

Comment 19

[Gabriele Svelto [:gsvelto]]

The crash volume has dropped to zero, and the actual underlying crashes all have bugs assigned to them. Shall we close this one?