-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
RealmList<RealmAny> on Android ARM devices works incorrectly #7626
Comments
Thanks for sharing the code example, it has allowed us reproducing the issue. While we are investigating the root cause for the issue we have noticed that it only affects ARM 32 bits, ARM 64 bits does not show the issue. Half of the devices you listed are |
@clementetb hello |
After running the example app on Testlab I confirm the devices in your list, although they might a 64bit SOC, run in 32bit mode in Testlab. |
Unrolled stacktrace of the crash:
|
I managed to compile a very small test case reproducing this only on ARM 32-bit in https://github.com/realm/realm-java/tree/ct/investigation-realmany. I have not yet been able to locate the actual root cause as the realm any immediately looks fine but is maybe ruined by a type cast. The debug session itself crashes without a proper indication of what goes wrong when trying to inspect the details, so will have to dig a bit more into the internals of the low level realm any implementation. |
This is fixed in 10.10.0. |
Expected results
List of RealmAny objects
Actual Results
List of "null" objects
Steps & Code to Reproduce
on realm-java 10.8.1 (realm-core 11.6.0) this sample crashing with next stacktrace:
on realm-java realm-java 10.9.0 (realm-core 11.7.0) getEntities(WithRealmAnyTestEntity::class.java) returns list of "null"
Can be reproduced on ARM devices:
SM-A105FN (API 29)
Nokia 1 (API 27)
Motorolla G5S (API 27)
Redmi 6A (API 27)
moto e5 play (API 27)
SM-G532G (API 23)
Nexus 5 (API 23)
LG-AS110 (API 23)
Nexus 7 (API 21)
Core version
realm-java 10.9.0 (realm-core 11.7.0)
The text was updated successfully, but these errors were encountered: