-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Synced Realm crashes with "Fatal signal 11 (SIGSEGV), code 1, fault addr 0xe0" during the first launch #6969
Comments
Hmm, it looks like an issue with a nullpoiinter instead of a C++ object given There should also be a native stacktrace. Are you able to post that? |
Thanks for the reply, @cmelchior.
|
Hi, @cmelchior
|
Is this problem solved?My app has also encountered this problem. |
We recently realased 7.0.2 containing a memory mapping management fix. I cannot see immediate indications from the traces that it should be exactly this, but maybe try to see if you can reproduct with 7.0.2. |
Hi, @rorbech
I think the same issue: |
Unrolled stack trace:
Which does seem to point to a problem with queries... |
@cmelchior |
It was mostly an internal note. Realm shouldn't crash like this, no matter what. So it is a bug on our end. Unfortunately, these kinds of bugs are really tricky to track down unless we can find a way to reproduce it. |
We have just released version 7.0.3 which includes more fixes regarding memory management. Please upgrade your dependencies and let us know if the problem is still present. |
@edualonso Thanks, will give it a try. |
Unfortunately, it crashed again with v7.0.3. I think it crashed before authentication and after the app restarted it was working fine
|
Unrolled stack trace:
|
@edualonso on 7.0.3 crash also reproduced. |
@VicMikhailau would you mind trying with version 7.0.4, we just released it today and it addresses further memory issues. |
@clementetb on 7.0.5 crash also reproduced. |
@VicMikhailau I am sorry to hear that. Are you able to reproduce this issue your self? Could you please share the steps it takes to reproduce the issue? |
@clementetb
When you first run these steps, everything is fine. After the second - crash (received only logs described above). Crash disappeared when:
Thanks. |
I have the exact same issue "A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)" when upgrading Realm from 5.14.0 to 7.0.5. Everything was fine until I see a crash at a specific step in a transaction. it seems to be related to I'm using right now 7.0.6 and I have always the same issue Note: I can reproduce this error easily. |
@sokarcreative That sounds great. If you have a way to reproduce this we would be very interested in seeing it. |
@cmelchior Tell me when you think you solved this issue and I will check if this crash persists. |
@cmelchior here is the stack trace, I hope it will help :
|
@sokarcreative Thank you. Can you post the model class you are doing the query on and the model class that is being referenced from the field you are checking. Also, are you using encryption? |
|
After looking at the unrolled stacktrace, it looks to be a duplicate of #7118 of which a fix was merged here realm/realm-core#3935. I'll attempt to get a 7.0.7 release out today which should hopefully fix this. |
Note: Kotlin was new at this time and extensions were so great x)
@cmelchior I will wait for the next release (7.0.7) if you think it solves it |
Realm Java 7.0.7 was released with a fix for this. |
It has been fixed ! Tested right now. On 7.0.6 crash then on 7.0.7 no more crash. 👍 |
@cmelchior Unfortunately, for my case, crash is still reproducible. I Will be waiting for the next release and make some fixes on my side. |
Goal
The app shouldn't crash
Actual Results
The app is crashing with
Steps & Code to Reproduce
This is usually happening when the realm is created for the first time. Sometimes we don't have any issues but sometimes it crashes on the first run(when there is no realm). I can see that the realm is created successfully using Realm Studio.
If it doesn't crash on the first run, it works flawlessly.
Stacktrace
Note that the package name, realm instance URL, class name, and IP address have been substituted with dummy values
Version of Realm and tooling
Realm version(s): 7.0.0
Realm Sync feature enabled: Yes
Android Studio version: 4.0
Android Build Tools version: 29.0.3
Gradle version:
Gradle 6.1.1 used with Android Gradle Plugin 4.0.0
Which Android version and device(s):
Android 5.1.1 running on TCL Xess P17AA tablet
The text was updated successfully, but these errors were encountered: