Fenix: FNX2-13669 ⁃ [Bug] java.lang.IndexOutOfBoundsException: at java.util.ArrayList.get(ArrayList.java)

Created on 24 Jun 2020  ·  14Comments  ·  Source: mozilla-mobile/fenix

This looks to be the top crash in the 20200622093309 Nightly.

Stacktrace

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.ArrayList.get(ArrayList.java:437)
    at mozilla.components.browser.search.SearchEngineManager.getProvidedDefaultSearchEngineAsync(SearchEngineManager.kt:7)
    at mozilla.components.browser.search.SearchEngineManager.getDefaultSearchEngineAsync(SearchEngineManager.kt:7)
    at mozilla.components.browser.search.SearchEngineManager$getDefaultSearchEngineAsync$1.invokeSuspend(Unknown Source:12)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:3)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:21)
    at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:1)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:11)
  • Android device: ?
  • Fenix version: 20200622093309 0.0a1 Nightly
SearchProvider crash engverified 🐞 bug

Most helpful comment

I put the 79 Release Blocker label on this because this is a very high frequency startup crash.

Looping in @Mugurell as this may be related to #11875

All 14 comments

This could be related to #9935 changes

We think this will also be fixed by #12081

https://crash-stats.mozilla.org/report/index/8cd6f146-2dc6-4f2c-a477-5b2140200703

null (Build #2015749827)
AC: 48.0.3, ce6247fb8
GV: 79.0-20200629163142
AS: 61.0.7
Friday 7/3 @ 8:43 AM

Looks like this made the top crasher list.

The last minute search changes really had a ripple effect and caused some issues. :( I hope we can try to get rid of the band-aid eventually.

I put the 79 Release Blocker label on this because this is a very high frequency startup crash.

Looping in @Mugurell as this may be related to #11875

Quick note: this crash is trending down in Sentry, but I think that is a false sign. I think a LOT of people hit this either at first run or a few times at startup, and then the situation resolved itself. That however does not change the fact that this is a high frequency startup crash. I've seen a number of reports on Reddit where people say they can't start the app, and this is probably one the reasons.

Indeed, I'm thinking that fixing #11875 (which is another effect for probably the same underlying issue) would also get to resolve this and a bunch recent others related to search engines.

Since we think the fix for #11875 may also fix this one, let's see if we can make sure this isn't still a problem.

While testing the fix for #11875 I didn't encounter any crashes on 79.0-beta6. @liuche Should I close this or do you want to continue monitoring the crash rates?

We released beta.8 and beta.9 today and I haven't seen any issues in Sentry, so let's close this now. Can reopen if it shows up again, but the last crashes I've seen have been from beta.3.

Was this page helpful?
0 / 5 - 0 ratings