-
Notifications
You must be signed in to change notification settings - Fork 179
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
Fix Crash in Multithread #18
Comments
Just some details about my situation (with the Python 3 fork): The bug was due to the destructor of JCleaner, the class that is used in JPype to clean up internal references, stored into PyCapsules (PyCObject in Python 2). I will try soon with the Python 2 version of jPype, maybe it's just a Python 3 evolution... |
Ah ok :) Btw thanks for your report and all the hard work :)! |
Hey @tcalmant are you still able to reproduce this with the latest commit? My tests still keep passing :S |
Hey @originell ! |
Glad to hear that! Thank you for testing :)! |
Any output from your second machine @tcalmant ? |
I've just finished my tests on a third machine, and the results are good. FYI, I'm running an OSGi framework (Apache Felix) with services shared between Java and Python, as a test. Maybe we should open an issue on both our forks, in order to prepare a small set of test scripts in Python 2 and 3, in order ensure compatibility and detect this kind of derivation. |
Ah, have to read up on Felix :) Don't know much about OSGi frameworks. Yeah that's a terrific idea to be honest :) Let's do this! |
I met a similar problem, and it shows that
I try code
but it doesn't work. What does the problem really mean? |
@tcalmant reported via mail that he found jpype crashing in multi-threading environments. I put this here because I think it's better to have it publicly in the bug tracker than in emails :)
He fixed it in one of his commits
Now we only need to test this with the changes from #17. Sadly I can't reproduce the error myself as it seems. So help is appreciated! :)
The text was updated successfully, but these errors were encountered: