-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Realm Swift abort() called
- Encrypted db getting corrupted and can't recover
#5190
Comments
➤ Jonathan Reams commented: [~finn.schiermer-andersen], have you seen any crashes like this before? |
Potential explanation: #5174 |
@palaniraja A clarifying question: The stack trace you've reported is from the second crash, right? |
Yes, most of the time first crash happened in the background. But atleast one instance was reported with first crash when app was in foreground. |
We may have a scenario that reproduce corruption of encrypted db consistently (realm-swift v10.21.0) If there is a commit we can test and report back |
ok I have some additional info this time. Instance 1:
Instance 2 & 3:
but both failed with different call stack wondering if any/all of these are related to #5174 |
Here you go another stacktrace with
|
➤ Finn Andersen commented: Fixed by realm-core 11.14 |
SDK and version
SDK : RealmSwift
Version: 10.21.1 (via SPM)
Observations
** Infrequent, but fatal error as our application db is encrypted
** Reported both in production as well as development. Production uses a old version 10.1.4 with carthage and dev 10.21.1 with SPM
** Yes, as we said not consistently but we can reproduced/observed it more than few times in last week
** Our app works in background (read/write to db) and after a day or two it stops (crashed in background), and when we try to launch manually app crash due to db is corrupted.
Crash log / stacktrace
Attaching the crashlog, stacktrace and lldb stactrace case as well
Mpapp 1-24-22, 10-20 AM.crash.txt
Myapp_crash.txt
stack_trace.txt
Steps & Code to Reproduce
Unfortunately we do not have one, will update the ticket if we figure out. Reporting it here, as from the stacktrace it is recommended to create issue on realm-core and previous issues on
abort called
is closed due to inactivity or older versionThe text was updated successfully, but these errors were encountered: