-
Notifications
You must be signed in to change notification settings - Fork 573
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
Fatal signal 11 (SIGSEGV), code 2, fault addr #3194
Comments
Thank you for reporting. I have a couple of follow-up questions:
|
I am developing only for Android on a Windows machine. Unfortunately I won't be able to test on iOS.
I had no problems with many smaller object transactions, I even tested with about 1 million small records and there was no crash.
The
Example of
|
Thank you for the update.
It indicates an issue in the underlying database, don't you agree @finnschiermer? |
Yes, I agree. If we can reproduce this it'll be a big step towards fixing it. |
➤ Finn Andersen commented: We have identified root cause of this, and a fix is being developed. |
@kevinpiske We have released v6.1.1 with a fix. |
Thanks all for the fast work! @kneth, in my case, the problem persists. Now the stack is not detailed anymore, the log is: I realized that the problem occurs when inserting data from two specific schemas. If I comment the inserting data of one these schemas, everything goes well. The problem only occurs by inserting data of these two schemas in separate transactions. Inserting data of these two schemas in the same transaction, it worked. |
@kevinpiske hey can you help me in my scenario.. i am facing same issue |
Goals
Insert large amount of data.
Expected Results
No crash.
Actual Results
The app crashs after the last Realm.write.
Steps to Reproduce
I believe this problem is relative to size of inserted data, because if inserts data of 0 to 4 offset, crash doesnt occurs.
Short Code Sample
The text was updated successfully, but these errors were encountered: