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

napari-imagej breaks with Jpype 1.5.1 #316

Closed
hinerm opened this issue Dec 3, 2024 · 2 comments
Closed

napari-imagej breaks with Jpype 1.5.1 #316

hinerm opened this issue Dec 3, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@hinerm
Copy link
Member

hinerm commented Dec 3, 2024

If I do a napari-imagej install from scratch with mamba create -n napari-imagej napari-imagej I currently get jpype1 1.5.1.

When starting up napari-imagej in this environment, napari hard crashes with this message on the command prompt:

image

Rolling back to jpype1 1.5.0 works as expected.

@hinerm hinerm added the bug Something isn't working label Dec 3, 2024
@gselzer
Copy link
Collaborator

gselzer commented Dec 3, 2024

This issue isn't specific to napari-imagej, as it can be repeated with a smaller MVCE:

  1. Create a conda environment: mamba env create -n tmp -c conda-forge pyimagej
  2. Run in python: import imagej; ij = imagej.init()
  3. Observe error:
Error occurred during initialization of VM
Could not find agent library instrument on the library path, with error: Can't find dependent libraries
Module java.instrument may be missing from runtime image.

This is likely a fix upstream in scyjava?

cc @ctrueden @elevans

@hinerm
Copy link
Member Author

hinerm commented Dec 3, 2024

@gselzer pointed out this is a reported issue in Jpype. It can be reproduced with import jpype; jpype.startJVM().

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

2 participants