Fenix: [Bug] ArrayIteratorKt in throwNpe in BrowserToolbar

Created on 12 Aug 2020  路  12Comments  路  Source: mozilla-mobile/fenix

Sentry: https://sentry.prod.mozaws.net/operations/firefox-beta/issues/9366156/?query=is%3Aunresolved%20ArrayIteratorKt

This has been around for a while, but seeing an uptick in 80.0.0-beta build.

kotlin.jvm.internal.ArrayIteratorKt in throwNpe at line 1
org.mozilla.fenix.browser.BaseBrowserFragment in getBrowserToolbarView at line 1
org.mozilla.fenix.browser.BaseBrowserFragment in onAccessibilityStateChanged at line 1
android.view.accessibility.AccessibilityManager in handleNotifyAccessibilityStateChanged at line 645
android.view.accessibility.AccessibilityManager in access$000 at line 68
android.view.accessibility.AccessibilityManager$MyHandler in handleMessage at line 691
E2 crash hershey uplift 馃悶 bug

All 12 comments

Do you know if this related to the browser toolbar consolidation changes that we made recently @person808 ?

We haven't made any toolbar changes that I'm aware of.

when you get back @mcarare could you take a look at this?

This looks to be several crashes grouped under a common signature. See https://crash-stats.mozilla.org/search/?signature=~throwNpe&product=Fenix&_facets=signature&_facets=java_stack_trace&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-java_stack_trace

@liuche I could try and add a check for that call, but IMO the main issue is with how we handle the reference to browserToolbarView, as we can identify multiple crashes cause by the getBrowserToolbarView call.

@liuche this change https://github.com/mozilla-mobile/fenix/pull/13880 should avoid the crash, but I will also keep an eye on this crash signature after the fix is merged and "live".

Thanks - this change makes sense, that we want this once the view is created, not always on start.

Looks like we're leaving this open to verify, since it's not QA-able.

Going to uplift this to the 80.0.1 beta channel.

Hey @mcarare we'd like to get this uplifted to the 80.0.0 release - could you open a PR against the releases/v80.0.1 branch? It wasn't a clean uplift.

I think this is okay to close, took a look at the Sentry logs and they seem to be decreasing a lot on beta.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bbinto picture bbinto  路  3Comments

phileastv picture phileastv  路  3Comments

softvision-miralobontiu picture softvision-miralobontiu  路  3Comments

thelazyoxymoron picture thelazyoxymoron  路  3Comments

abodea picture abodea  路  3Comments