-
Notifications
You must be signed in to change notification settings - Fork 308
Crash caused by libobjectbox-jni.so at __cxa_pure_virtual function #1131
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
Comments
Thanks for reporting! Relevant stack trace section:
Is this project actually using version Let me know if the issue persists after updating. This issue will auto-close in 2 weeks if there is no response. |
@jobernolte Thanks! I've tried to run the tombstone through the ndk-stack tool, but without success. I guess the Play Developer Console does not give any additional info? As is, it is kind of hard to see why the crash occurred. Based on the stack trace it looks like an exception from a query subscription. Does that help you pinpoint potential code locations? A potential cause may be a query subscription that is not cleaned up properly before e.g. closing the store. Though this should typically trigger a Java exception, not a JVM crash. Edit: a similar trace was reported at #1081 (comment). This issue will auto-close in 2 weeks if there is no response. |
I'm using a generic ObjectBox database with two locations were I subscribe to a query.
and
Does this help? |
And there are other stack traces which I found in the Play Console:
|
|
And this one:
|
These traces all appear to have this in common:
We're looking at this internally on how this can happen. |
We have released version If you get related exceptions, they should contain additional information to better diagnose this issue. Please let us know. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Some of our users experience crashes of our App caused by the ObjectBox library.
Basic info (please complete the following information):
To Reproduce
not applicable
Expected behavior
The App should not crash ;)
Logs, stack traces
The text was updated successfully, but these errors were encountered: