[iOS only] Realm crash: EXC_BAD_ACCESS KERN_INVALID_ADDRESS #3913
Labels
Comments
|
@mklb Thank you for the bug report. We have seen some reports on We have two bug fixes in v10.6.2-beta.1 related to mixed and links (one is related to sync). Can you explain how you are using mixed so we can see if the fix will apply to your app or it is a new bug? |
|
@kneth Thank you for the quick response! Are you referring to the 'mixed' data type which is in beta? I am not using it and was not aware that it existed until now. |
sync-by-unito
bot
added
the
More-information-needed
Yes, I am referring to the new mixed data type.
This is interesting information. The stack trace mentioned mixed ( Do you call any aggregation function ( |
|
I am not using The most exotic thing I use for queries is Does I found this old code: Maybe this could be problematic? (I should use $1 for someId) Apart from these two calls, I just use The weird thing: I never had a |
no-response
bot
removed
the
More-information-needed
|
The In the past, we have had report on crashes of apps in production and never in development. Something it has been related to the app being suspended. One user solved the issue by writing some code to handled the situation where the app is suspended: #3162 (comment) I don't if this is applicable to your case. |
|
Thanks for the quick response! Is there anything else I could do to help out / find that bug? I just released my app with realm |
|
11 new crashes with I may have found some similarities in the user journey this time. unlockSomething(otherRealmObject) {
this.realm.write(() => {
this.userState.coins -= otherRealmObject.coins
this.userState.lastChanged = new Date()
})
}
However, this code may looks more dangerous due to the use of Remote Config from react-native-firebase earnSomeCoins(someObjects) {
var coins = 0
for (let i = 0; i < someObjects.length; i++) {
// do bunch of other stuff and..
coins += remoteConfig().getValue('coin_reward_for_event_X').asNumber()
}
this.realm.write(() => {
this.userState.coins += coins
})
} |
|
Received a different error log for the same crash now. |
|
Hey! I'm having the exact same crash log. For me this crash happens when app is woken in background by |
|
I was experiencing the same issue on my iOS simulator (iOS 15.0, iPhone 12) using RealmJS |
|
Just got my first 8 crash reports in production with iOS |
|
All reported crashes were with |
|
Same issue here with realm 10.8.0. |
3 tasks
|
Thanks all for reporting this issue! We've released Realm-JS v10.9.1, which addresses a memory leak in the |
|
@fronck Thank you! |
|
@fronck I have just released my app with realm 10.9.1 to 1% of iOS users. EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000118 |
|
@fronck I have other users with the same crash. Considering the very limited amount of people I released the app to, the fix seems to make the app crash even more than the original bug. Can I rollback to 10.0.3 which was working fine for me, or has the data structure changed? I'd like to avoid #4016, #3913 and #4007. |
|
@fronck I just got the same crash like @Pingou , however I am still running |
|
There is also another new crash that no one mentioned, yet ( |
|
➤ Patrick commented: There is also another new crash that no one mentioned, yet ( |
|
@mklb Please try to upgrade to v10.9.1. |
|
@kneth updated to v10.9.1 - Released the update to 100% of my users. So far I do not see the same crashes as above but I already got a new one from a iOS 15.0.2 user. |
|
@mklb Thanks for the feedback. I'll reopen the issue and we'll investigate the new stack traces. |
|
I just saw that the crash above is the same as my crash report from the 9th of Jul. #3602 (comment) . I can add that I have this crash happened a second time with the same Realm version |
|
Getting same crash reports same as @mklb posted. crash analytics indicates this happens 100% when device states Realm Crash report |
|
for summary there is two crash reports posted here and we see it in crash logs that effects most of our users on realm
The device state for all the crashes is 100% in background and the crash is not related to a specific iOS version.
Crash report 1Crash report 2Crash report 3 (Not posted here) |
|
@taikim8484 Unfortunately I couldn't find the cause of this crashes so I kinda gave up, it's effected more than 10k of our user base, but we haven't received any report regarding this crashes from our users, so I assume user's are not noticing this crashes as all of them happening in the background. looks like this crash started to appear after upgrading from |
Closed
|
As our JSI implementation (version 11) is under way, we ask you to upgrade to v11.0.0-rc.1. I am closing the issue, and if it is still observed after upgrading, please create a new issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How frequently does the bug occur?
Sometimes
Description
I have 26 crashes in production precisely like this from 23 different uses. The crashes happened in various stages of the user journey, so I can not pinpoint it to any specific time when my code is interacting with Realm..
One user reported that the app crashes after using it for a long time (the whole day). The app would not open again after the crash. Just deleting and installing would fix the problem. -> This somehow sounds like the database would be corrupt, which would be the only reason to prevent the app from launching again.
Stacktrace & log output
Can you reproduce the bug?
Not yet
Reproduction Steps
None.
Version
10.6.0
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS: 14.6.0 & 14.7.1 (nearly 50/50 distribution)
Build environment
The text was updated successfully, but these errors were encountered: