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

Crashing during initiation of drift correction #3

Open
Nivoko opened this issue Jan 29, 2021 · 5 comments
Open

Crashing during initiation of drift correction #3

Nivoko opened this issue Jan 29, 2021 · 5 comments

Comments

@Nivoko
Copy link

Nivoko commented Jan 29, 2021

Hi,
as in the other issue, Fiji just keeps on crashing as soon as I use anything from NanoJ.
I uninstalled it, reinstalled it, issue persisted, reinstalled Fiji, tried again and failed again.
I tried different files but to no avail. It seems that the plug-in doesn't work at all.

Does anyone have the same problem?
Does anyone has any further suggestions?
How much RAM do I need for NanoJ to run properly given that my files are between 230mb and 2gb?
(I use Win10, 8gb RAM, i5...)
Is there a preferred Fiji or Java version on which it should run?

Any advice is much appreciated!

I do generate an error log file which is attached.
hs_err_pid336.log

@DeboraOlivier
Copy link

Hellom I hqve the same issue: I just downloaded and installed the latest version of NanoJ-Core via the update site, and restarted fiji before trying to run Drift Correction on an open image
492mb but I have 16G RAM so that should work

it crasshed Fji and closed the program, twice now.
Any idea?
Cheers

Debbi

@lauracmurphy
Copy link

lauracmurphy commented Apr 26, 2022

Just to add that I also have this issue, that clicking "Estimate Drift" in drift correction closes FIJI even if an image isn't open. I've seen this behaviour on a few computers, all Window 10.

@JohannaRahm
Copy link

I have the same problem. ImageJ version 1.53q, Java 1.8.0_172

@lauracmurphy
Copy link

For the people still struggling, I installed OpenCL based on what was said here and it fixed the issue.

@HannahSHeil
Copy link

There is also a description of a fix for Windows users here.

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

5 participants