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

Morphological Segmentation crashes if stack too big? #10

Closed
Mathieu-Prouveur opened this issue Aug 21, 2017 · 2 comments
Closed

Morphological Segmentation crashes if stack too big? #10

Mathieu-Prouveur opened this issue Aug 21, 2017 · 2 comments

Comments

@Mathieu-Prouveur
Copy link

Hello,

I am currently using your plugin to label 2D videos of cells and depending on the computer I use, the morphological segmentation command may freeze Fiji.

For instance I tried to open this stack :
filteredimage

And here is what I get, when it crashes Fiji doesn't respond anymore and the morphological segmentation window is always blank with the 3200% tag :
crash

However if I take a substack, the plugin works perfectly fine and it also does if I pick an even better computer.

So I guess it is related to the computer resources. But still I am surprised that it crashes for a 6Mo stack with 70 slices on a computer with 83.4GHz CPU,48GB RAM,4GB AMD Radeon HD7900 whereas it doesn't crash on a computer with 20*3GHz CPU,64GB RAM, 4GB AMDFirePro W5100 even if i copy the stack 100 times so as to try the same command on a 7000 slices stack.

I would be very interested to have your opinion on the subject and to know if there is any solution other than sticking to the better computer.

Thanks a lot for your work, so far the library is great anyway!

@iarganda
Copy link
Contributor

Hello @Mathieu-Prouveur,
This is a known issue that has to do with the dimensions of your screen and the height and width of your input image being too small to zoom to 512x512 as required by the plugin GUI (so the GUI falls into an infinite loop of zooming). The bug has been fixed, so just wait a bit for the next release (coming very soon!).

@Mathieu-Prouveur
Copy link
Author

Great, thanks for the quick answer! I am still a bit puzzled by the fact that it worked fine with a substack though ^^' I'll wait for the next release then !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants