-
Notifications
You must be signed in to change notification settings - Fork 163
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
Crash: Invalid mnemonic #3134
Comments
This was referenced Oct 30, 2018
➤ Brian Munkholm commented: Seen in Java 6.0.2. |
No activity for a year now -> closing |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We are seeing a number of crash reports on the Java side that indicates the Realm file is somehow being corrupted. It is still unclear why this is happening, but the errors all have the same form but with different values:
Fatal Exception: io.realm.exceptions.RealmFileException: Unable to open a realm at path '/data/data/com.test/files/userdb.realm': Invalid mnemonic. top_ref[0]: 104600030316, top_ref[1]: 623E3EBB12044142, mnemonic: A7 8C EE A, fmt[0]: 160, fmt[1]: 49, flags: D7. (Invalid mnemonic. top_ref[0]: 104600030316, top_ref[1]: 623E3EBB12044142, mnemonic: A7 8C EE A, fmt[0]: 160, fmt[1]: 49, flags: D7) (/data/data/com.test/files/userdb.realm) in /Users/cm/Realm/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 101
References to Java issues:
Current observations:
userdb.realm
while Crash: Top ref outside file #3133 only happens for thelibrarydb.realm
. This could indicate these files are somehow being handled differently as they seem to become corrupted in different ways. I'm trying to verify this.Known devices that has experienced this error:
Crash data:
A list of exceptions and devices it is happening on can be seen here:
The text was updated successfully, but these errors were encountered: