Open Bug 1814129 Opened 2 years ago Updated 10 months ago

Debug build crashes at startup on older devices

Categories

(Fenix :: Performance, defect, P3)

All
Android
defect

Tracking

(Performance Impact:low)

Performance Impact low

People

(Reporter: boek, Unassigned)

Details

From github: https://github.com/mozilla-mobile/fenix/issues/17920.

Steps to reproduce

Install latest debug build from https://firefox-ci-tc.services.mozilla.com/tasks/index/mobile.v2.fenix.debug.latest/arm64-v8a

Crash:

02-08 10:56:02.185 21990 21990 E AndroidRuntime: FATAL EXCEPTION: main
02-08 10:56:02.185 21990 21990 E AndroidRuntime: Process: org.mozilla.fenix.debug, PID: 21990
02-08 10:56:02.185 21990 21990 E AndroidRuntime: java.lang.RuntimeException: StrictMode ThreadPolicy violation
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.StrictMode$AndroidBlockGuardPolicy.onThreadPolicyViolation(StrictMode.java:1768)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.StrictMode$AndroidBlockGuardPolicy.lambda$handleViolationWithTimingAttempt$0$StrictMode$AndroidBlockGuardPolicy(StrictMode.java:1687)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.-$$Lambda$StrictMode$AndroidBlockGuardPolicy$9nBulCQKaMajrWr41SB7f7YRT1I.run(Unknown Source:6)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:883)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:100)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:237)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:8167)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: Caused by: android.os.strictmode.DiskReadViolation
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.StrictMode$AndroidBlockGuardPolicy.onReadFromDisk(StrictMode.java:1556)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.sqlite.SQLiteConnection.applyBlockGuardPolicy(SQLiteConnection.java:1524)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.sqlite.SQLiteConnection.executeForCursorWindow(SQLiteConnection.java:1193)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.sqlite.SQLiteSession.executeForCursorWindow(SQLiteSession.java:838)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.sqlite.SQLiteQuery.fillWindow(SQLiteQuery.java:62)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:165)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:152)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:232)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.database.AbstractCursor.moveToFirst(AbstractCursor.java:271)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.enterprise.storage.EdmStorageProviderBase.getValues(EdmStorageProviderBase.java:388)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.enterprise.storage.EdmStorageProviderBase.getValuesList(EdmStorageProviderBase.java:1104)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.enterprise.storage.EdmStorageProvider.getValuesList(EdmStorageProvider.java:300)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.enterprise.application.ApplicationPolicy.getApplicationStateEnabledAsUser(ApplicationPolicy.java:3745)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.enterprise.application.ApplicationPolicy.getApplicationStateEnabledAsUser(ApplicationPolicy.java:3714)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.pm.PackageManagerService.setEnabledSetting(PackageManagerService.java:26031)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.pm.PackageManagerService.setComponentEnabledSetting(PackageManagerService.java:26007)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:3774)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:5145)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.Binder.execTransactInternal(Binder.java:1056)
02-08 10:56:02.185 21990 21990 E AndroidRuntime: 	at android.os.Binder.execTransact(Binder.java:1029)

Device information

  • Device vendor / model and Android version: Samsung S10e, Android 10

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

mcomella had mentioned the idea of enabling strict mode in Nightly here, but that's probably a bit too extreme.

For now, if someone picks this up, please consider alternative ways of getting more information about this crash - e.g., logging strict mode warnings to Sentry, or (if viable? - would need to check with RelMan) creating a build that rolls out to a very limited percentage of installations (e.g., distribute it to 1-3% of nightly users).

So, to clarify: the priority for this bug current represents the task of "getting more information" - we likely don't have any actionable fix ready to be worked on right away.

Severity: -- → S4
Priority: -- → P3

The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.

Platforms: Android
Impact on browser: Renders browser effectively unusable
Configuration: Rare
Websites affected: Rare
[x] Able to reproduce locally

Performance Impact: --- → low
You need to log in before you can comment on or make changes to this bug.