Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Synch methods crash #21

Open
dkrikun opened this issue Sep 7, 2011 · 2 comments
Open

Synch methods crash #21

dkrikun opened this issue Sep 7, 2011 · 2 comments
Labels
critical

Comments

@dkrikun
Copy link
Owner

dkrikun commented Sep 7, 2011

Synchronized methods crash with 'using JNIEnv from the wrong thread' which is pretty weird because jni is supposed to be reloaded prior to each use. The crash probably happens on lock comparison. Sometimes, instead of crash the comparison result is just non-deterministic.
This is a serious bug, but we can live without synch. methods being checked by eraser in the worst scenario.
@dkrikun
Copy link
Owner Author

dkrikun commented Sep 7, 2011

The bug is not caused by method synch, but rather by threads having not a common lock.
Somehow thread operator== is invoked when the universal set is already empty. Should it be invoked?

dkrikun added a commit that referenced this issue Sep 7, 2011
@dkrikun
Debugging issue #21.
a81b94b
@dkrikun
Copy link
Owner Author

dkrikun commented Feb 14, 2013

Good bye!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
critical
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dkrikun