Napari crashes when opening images after the plugin has been opened

[zoccoler]

Hi guys,

I wanted to try out the cellpose-napari plugin! So I installed it with the following commands on a Windows 10 machine:

conda create -n napari-cellpose-env python=3.9
conda activate napari-cellpose-env
conda install -c conda-forge napari
pip install cellpose-napari

Then, I can open the plugin via the Plugins menu. However, after that, if I try to load any images, napari crashes and I get the following error message in the terminal:

OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.

This also happens whenever I try to open one of the cellpose-napari sample images.

The only way I could make it work is to open the image (not the sample ones though) before opening the plugin.

If you know what's causing this or need more information, let me know :)

Best,
Marcelo

Some relevant package's versions

python 3.9.13
napari 0.4.14
cellpose-napari 0.1.5
torch 1.12.1

[zoccoler]

Update and possible solution:

So now I installed napari 0.4.16 and cellpose-napari in a new conda environment, both with pip and this error is gone.

pip install napari[all]
pip install cellpose-napari

Within this environment, I can also open the sample images from cellpose-napari after the plugin has been opened. So I guess this could be about the napari version.

If anyone can confirm this, feel free to close the issue.