-
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
Crash when changing dictionary nullability during migration #7781
Comments
github-actions
bot
added
Encryption:On
Frequency:Always
Repro:Always
SDK-Use:Local
labels
Mar 2, 2023
Hi @RakeshPatil111. Thanks for the report. I am able to reproduce it and will investigate. |
Thanks, hope we can find something. |
rorbech
changed the title
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
Crash when changing dictionary nullability during migration
Mar 3, 2023
It points out to be a core issue. I have created an issue in core to track this: realm/realm-core#6408 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How frequently does the bug occur?
Always
Description
I am unable to use app as it is crashing always.
I have a migration function, in which I have a line which making realDictionary field required.
After executing that line app is crashing
schema.setRequired("fieldName", true)
Initially this RealmDictionary field was nullable.
var data: RealmDictionary<String> = RealmDictionary()
Stacktrace & log output
13:22:34.628 6804-6935/compackage.name A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 6935 (androidx.work-1), pid 6804
Can you reproduce the bug?
Always
Reproduction Steps
Version
10.6.0
What Atlas App Services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
Android 10+ [API 30+]
Build environment
Android Studio Bumblebee | 2021.1.1 Patch 3
Build #AI-211.7628.21.2111.8309675, built on March 16, 2022
Runtime version: 11.0.11+9-b60-7590822 amd64
VM: OpenJDK 64-Bit Server VM by Oracle Corporation
The text was updated successfully, but these errors were encountered: