-
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
EXC_BAD_ACCESS on version 5.x.x #6626
Comments
Our app is crashing on lauch 4 out of 5 times due to this. |
@raphaelcruzeiro @trr-amsiq Can you please provide details of the crashes? And if this is reproducible, can you try to make a minimal reprocase? |
@bmunkholm I have EXC_BAD_ACCESS happening all over the place since the 5.x.x update. I've actually copied a stacktrace to the other EXC_BAD_ACCESS issue (#6555) since it seems it's the same method that is crashing. I'm trying to get all the stacktraces but they are taking a while to arrive since the app is crashing on lauch. So far I've observed EXC_BAD_ACCESS on the following spots:
I'll post to this thread again if I get the stacktrace for Also, I can't be 100% sure if this is related, but we started receiving quite a lot of |
This is the stacktrace on app launch with 5.3.0. from 4.4.1.
The code causing the crash is and is within a write transaction:
|
Seems to be related to #6555 |
@raphaelcruzeiro @trr-amsiq are you running with encryption enabled? |
It is a no from here |
@jedelbo also not enabled here |
@raphaelcruzeiro @trr-amsiq ok - then this is not encryption related. |
I tried both scenarios and it doesn't matter if the file was upgraded or not. I will try to get you the realm files. Don't expect them today. |
I tried reproducing the crash on a simulator. It just won't happen. |
Probably fixed by realm/realm-core#3828. |
!!! MANDATORY TO FILL OUT !!!
Actual Results
Crashes in
Version of Realm and Tooling
Realm framework version: 5.0.3 and 5.2.0
Xcode version: 11.5
iOS/OSX version: iOS 12 and 13
Dependency manager + version: SPM
The text was updated successfully, but these errors were encountered: