-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug]Crash when trying to access Saved Logins for the second time while performing a Sync #7344
Comments
Should be fixed by mozilla-mobile/android-components#5715 |
Hi @ekager , still reproducible on the latest ► Video from Google Pixel 3a XL -------- beginning of crash
2020-02-24 17:24:48.138 6693-6775/? E/AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-6
Process: org.mozilla.fenix.nightly, PID: 6693
mozilla.appservices.logins.LoginsStorageException: Using DatabaseLoginsStorage without unlocking first
at mozilla.appservices.logins.DatabaseLoginsStorage.checkUnlocked(DatabaseLoginsStorage.kt:2)
at mozilla.appservices.logins.DatabaseLoginsStorage.access$checkUnlocked(DatabaseLoginsStorage.kt:1)
at mozilla.appservices.logins.DatabaseLoginsStorage.list(DatabaseLoginsStorage.kt:4)
at mozilla.components.service.sync.logins.AsyncLoginsStorageAdapter$list$1.invokeSuspend(AsyncLoginsStorage.kt:4)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:2)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:15)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:1)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:15)
2020-02-24 17:24:44.736 1769-1769/? V/DeadZone: consuming errant click: (223.0,41.0)
2020-02-24 17:24:48.143 1323-1890/? W/ActivityTaskManager: Force finishing activity org.mozilla.fenix.nightly/.App
2020-02-24 17:24:48.143 1323-7746/? I/DropBoxManagerService: add tag=data_app_crash isTagEnabled=true flags=0x2
2020-02-24 17:24:48.147 1323-8946/? E/libc: Access denied finding property "vendor.debug.egl.changepixelformat"
2020-02-24 17:24:48.147 1323-8946/? E/BufferQueueProducer: [unnamed-1323-23] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
2020-02-24 17:24:48.147 1323-8946/? E/Surface: IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
2020-02-24 17:24:48.152 1323-8946/? E/libc: Access denied finding property "vendor.debug.egl.swapinterval"
2020-02-24 17:24:48.162 1323-1411/? W/BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
2020-02-24 17:24:48.162 1323-1411/? W/BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
2020-02-24 17:24:48.178 6693-6775/? I/Process: Sending signal. PID: 6693 SIG: 9
2020-02-24 17:24:48.258 7050-7050/? W/yya: Failed to find local clusters.
2020-02-24 17:24:48.269 7050-7759/? E/sef: Interactive Ads jobs: did not expect this future to ever resolve
2020-02-24 17:24:48.272 1769-1769/? D/InterruptionStateProvider: No heads up: unimportant notification: 0|org.mozilla.fenix.nightly|1|mozac.lib.crash.notification|10386 |
Sorry for any confusion! No fix for mozilla-mobile/android-components#5715 has landed yet but we think that fix will also fix this :) |
Should be addressed by #8875 |
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
Hi, verified as fixed on both |
The a-c side of this work is in mozilla-mobile/android-components#6128 This switches Fenix to use `SyncableLoginsStorage`, which caches a connection internally on first access, and doesn't expose any lock/unlock APIs at the public boundary.
Prequisites
User should be signed in to sync.
Steps to reproduce
Expected behavior
The Saved logins should be displayed
Actual behavior
Crash
Device information
Android device:
• Google Pixel 3a (Android 9)
• Samsung Galaxy S7 (Android 7)
Fenix version: Nightly Build #13570608 from 12/23
Notes
Not reproducible 100%
Didn't manage to reproduce on:
• Huawei Mate 20 Lite (Android 8.1.0)
• OnePlus A3 (Android 6.0.1)
• LG Nexus 4 (Android 5.1.1)
► Video
![20191223_144710](https://user-images.githubusercontent.com/51314259/71360143-7ddac480-2597-11ea-89cb-7ca0b058c941.gif)
► Logcat
@csadilek & @jonalmeida - Seems to app-services related?☺️
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: