-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Issue using Realm with Swift Actors #7901
Comments
Hi @brenmcnamara Could you show us code samples of how you are using Realm at the crash site? Also some details about your object schema would be helpful. |
Brendan's teammate filling in here. We initially thought rolling back to 10.20.0 had resolved these crashes, but that appears to not be the case. Instead, we're seeing a similar volume of similar looking crashes. All of these crashes occur within a few seconds of app launch. Here are some examples: Crash 1
Crash 2
Because these crashes continued after we reverted to 10.20.0 and are significantly higher in volume than before we upgraded to 10.28.1, my theory is that 10.28.1 somehow caused corruption in an elevated percentage of users' databases. All reads and writes to Realm in our codebase are serially executed on a dedicated reader or writer Actor. |
Thanks @t-sakhuja for providing the details above. |
@t-sakhuja can you show us the Actor which coordinates the reads and writes? |
@leemaguire here you go
|
same crash at 1 second
|
realm::util::terminate
crashes
Confirming we are still seeing the issue, currently preventing us from updating Realm. |
Following up here. We are a few versions behind on Realm at this point, and are looking to upgrade, but this bug here is blocking us from upgrading to the latest version of Realm. Could these crashes have been caused by the problem fixed in this PR? |
How frequently does the bug occur?
Sometimes
Description
We are receiving a number of crashes in our production application (1000+ crashes). These crashes began happening after we upgraded from Realm 10.20.0 to 10.28.1. In our latest release, we have reverted back to Realm 10.20.0 and these crashes have stopped happening. We are having a hard time diagnosing what is causing the crash and cannot reproduce these locally, but the stack traces we see in Crashlytics indicate that they are happening in
realm::util::terminate
calls (including stack traces below). Some things we are observing:realm::util::terminate
call which is throwing the error.Stacktrace & log output
Can you reproduce the bug?
Not yet
Reproduction Steps
No response
Version
10.28.1
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS 15, iOS 16, iPadOS 15
Build environment
Xcode version: 13.4.1
Dependency manager and version: Cocoapods Version 1.11.3, Realm Version 10.28.1
The text was updated successfully, but these errors were encountered: