-
Notifications
You must be signed in to change notification settings - Fork 173
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 Write Crash #6593
Comments
We cannot say for sure if this is fixed by #6411 without a repro-case, but it could be worth trying out the newest release and see if it is fixed. |
@finnschiermer We did upgrade to Swift SDK 10.38.0 and saw a slight reduction in cash rate (currently seeing ~0.5% of users encountering the issue) but ultimately we are changing the way we write to realm to a single serial background queue which seems to be the recommendation. We will be releasing the new update to our users in the coming weeks so hopefully we will have some positive news to report. |
@dlbuckley could you tell which original version worked fine for you (before first upgrade)? |
@kiburtse 10.33.0 Sorry for the slow reply, I must have missed the notification. As an update; this is still a long running issue for us. |
@jedelbo I just wanted to follow up on this ticket and say thank you for finding and fixing the core of this issue in #6962. We have been slowly rolling this out to our users and have seen this issue practically vanish. I know it was a difficult one to find but the efforts are paying off. Thank you! |
How frequently does the bug occur?
Sometimes
Description
We recently upgraded to Realm 10.37.2 and have seen no issues during our internal testing. We released a new app update which included the new Realm version yesterday and have started to see a spike in crashes related to some internal realm issues.
They all seem to happen in their own background serial queue.
This could be related to #6411 but I'm not sure and would love some clarification on this rather than sending out a speculative fix.
Stacktrace & log output
The text was updated successfully, but these errors were encountered: