-
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
Native crash with findFirst() reproducible with 7.0.2 #7043
Comments
Note: with 6.1.0 we did not have any problem, now I started to see these since 7.X.X |
Crash also reproduced after updating from 6.1.0 to 7.0.1 or 7.0.2:
I think the same issue: |
@beczesz I am not able to reason about the root of this from the stack traces. Are you able to supply some details on whether it is an occasional or persisting error and do you have the Realm file that causes this? |
@beczesz
Main point: large data saved and retrieved from DB. On 6.x.x versions all work as expected. |
Unforunately I don't have the realm file anymore. I had to delete the database in order to be able to start the app. Next time if I can catch it I will save it. |
Is there a private channel where I can send you a database file? I would not post it in public. |
@beczesz Yes, you can send it to claus.rorbech (at) mongodb.com |
Ok, we decided that we will roll back to 6.1.0 for every user because 7.X and 10.X was unstable. We saw this especially on Samsung devices and OnPlus devices, but on others too. The database got corrupted on: schema migration, realm file format migration, and simply by using it after a while it got corrupted after a while. If anybody is interested how we did it then please let me a message. |
Unrolled stack trace from OP (Core 6.0.17):
|
➤ Finn Andersen commented: Happens while descending the cluster tree |
@beczesz Are you saying you can reproduce making the database crash? If so, we would be really interested in knowing the steps to take? |
@beczesz Today we released version 7.0.4. It addresses several memory issues and searching objects by primary key. Would you mind checking if the issue persists? |
Hi @clementetb ok I can check it, but only tomorrow. I get back to you. |
@cmelchior unfortunately I'm not sure if I can reproduce this exact crash, but I can reproduce other types of crashes.Tomorrow I will make some tests and get back to you regarding 7.0.4 |
Note, we just released 7.0.5 with more fixes. |
This might also be fixed by realm/realm-core#3904. We'd very much like to know if it persists after upgrading. |
We released 7.0.6, with a new fix. It shouldn't be related to this, but would be nice to hear if you can still reproduce using this version. |
@cmelchior unfortunately, in my case, the crash is still reproducible. |
We should be aware the the issue reported by @VicMikhailau is not the same as the original issue here. As I think we have fixed issues around "find_first", I take the liberty to close this issue. If you find that there is still an issue around "find_first", please reopen. For other problems - please create new issue. |
When I execute a query with findFirst() now it throws an exception all the time findAll() and then accessing the first element works fine.
The text was updated successfully, but these errors were encountered: