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

crash with jpype1=1.5.1 #122

Open
carlocastoldi opened this issue Nov 24, 2024 · 2 comments
Open

crash with jpype1=1.5.1 #122

carlocastoldi opened this issue Nov 24, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@carlocastoldi
Copy link

Since the release of jpype=1.5.1 paquo crashes the interpreter on paquo.java import.

This is likely due to QuPath shipping a partial copy of the JVM, as explained in jpype-project/jpype#1242. This makes jpype crash by not finding java.instrument

@ap--
Copy link
Collaborator

ap-- commented Nov 25, 2024

Thank you for the report @carlocastoldi ❤️

I'll monitor the jpype issue, and in case there is no workaround, will release a new paquo version next week with a jpype version restriction.

@ap-- ap-- added the bug Something isn't working label Nov 25, 2024
@helmut-hoffer-von-ankershoffen
Copy link

helmut-hoffer-von-ankershoffen commented Nov 25, 2024

Can confirm the issue on macOS X. Currently having to workaround by adding dependency to jpype==1.5.0 when depending on paquo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants