-
Notifications
You must be signed in to change notification settings - Fork 168
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
Slab allocator crashes deleting a block #6922
Comments
Hello, thank you for reporting this, this seems compatible with the generic issue that tracks all the free list corruptions we have had so far (#6813). I'll add this new issue in there as well. We are trying to understand what it is, that it might have caused a corruption in the free list. Unfortunately, at the moment we have no solution, since we haven't found a way to reproduce it. However, it seems your app is highly impacted by this, do you happen to have some more info to share with us? For example, what these apps that are crashing were doing when they were auto updated? Does your app use Also, thanks for the range of realm core versions, I'll look in all the commits that went in and try to understand what could have caused such regression. |
Our default Realm configuration uses a file based encrypted realm. We do provide a function to Realm.Configuration(
fileURL: fileURL,
encryptionKey: encryptionKey,
schemaVersion: schemaVersion,
migrationBlock: env.performDatabaseMigrations(_:_:),
shouldCompactOnLaunch: env.shouldCompactDatabaseOnLaunch(totalBytes:usedBytes:)
) So far I haven't been able to identify a common pattern in the crashes, it happens across the app when adding and updating entries in write transactions. Do you have any recommendations for a temporary solution? would downgrading Realm cause other issues or is passing a value for compacting a potential cause? |
At the moment we don't know what it is causing this, unfortunately. We have several ideas, but we haven't been able to identify the root cause of this issue. So I can't give you any advice that is based on some strong foundation. |
No our app does not use the Realm sync feature. |
If it's a data point, we are experiencing this issue and have not been able to reproduce reliably We do not specify For us, we also started seeing it in realm-swift 10.33.0 and we currently use realm-swift 10.38.0, so that's realm-core 12.13.0 to 13.9.0 according to the release notes, which maybe can narrow it down a little for bisecting |
SDK and version
SDK : Swift
Version: 10.42.0
Observations
Crash log / stacktrace
Steps & Code to Reproduce
This is closure #1 in
Profile.updateLastSeenLocal
referenced in the stack traceThe text was updated successfully, but these errors were encountered: