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.

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

Segfault on invoke of interface methods #445

Thrameos opened this issue May 24, 2019 · 1 comment


None yet
1 participant
Copy link

commented May 24, 2019

During testing of the _jcollection classes, retainAll resulted in a hard crash on windows. Unable to get a core dump as of yet.

@Thrameos Thrameos added the bug label May 24, 2019

@Thrameos Thrameos self-assigned this May 24, 2019

@Thrameos Thrameos changed the title Segfault on ArrayList retainAll Segfault on invoke of interface methods May 25, 2019

@Thrameos Thrameos added this to the JPype 0.7 milestone May 25, 2019


This comment has been minimized.

Copy link
Contributor Author

commented May 25, 2019

It was a repeat of the bug that I thought I was testing against a few days back. JPype used CallNonvirtual* methods of JNI. This is fine if the method actually exists. But if the method is abstract well down goes the JVM. It took forever to debug because most of the crashes went down so hard that error log was dying in some place like the garabage collector or the interrupt handler. Finally got one attempt to crash with a meaningful backtrace and ran it to ground.

@Thrameos Thrameos closed this in 71cb9c4 May 31, 2019

Thrameos added a commit that referenced this issue May 31, 2019

Merge pull request #447 from Thrameos/collection_test
Fix virtual method bug. Fixes #445, Fixes #441
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.