-
Notifications
You must be signed in to change notification settings - Fork 154
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
new_object: accessed stale local reference #44
Labels
Comments
ah crap. Can you roll your version of the jni crate back to 0.5.3 and try again? I bet it's the most recent change that did it. |
Yeah, that works! 🎉 |
jrobsonchase
added a commit
that referenced
this issue
Sep 25, 2017
jrobsonchase
added a commit
that referenced
this issue
Sep 25, 2017
jrobsonchase
added a commit
that referenced
this issue
Sep 25, 2017
OK, grab version 0.6.1 now. Should be fixed! |
Can confirm! :) Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a simple POJO class with an empty constructor.
This is what the JNI class looks like according to
javap
:When I try to create a new instance for that class:
...then I get a native crash.
Any idea what reference that could be? I've tried to debug this for quite a while now.
The text was updated successfully, but these errors were encountered: