NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 1170 - Fiji slow to startup
Fiji slow to startup
Status: RESOLVED DUPLICATE of bug 933
Product: Fiji
Classification: Unclassified
Component: Other
unspecified
PC Windows
: P5 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2015-10-06 05:23 CDT by amc910
Modified: 2015-10-13 11:05 CDT
1 user (show)

See Also:

Description amc910 2015-10-06 05:23:19 CDT
Hi there,

Fiji takes ~10-20 minutes to load up on certain computers in our group.
This seems to be a similar issue to Bug 933, but that thread seems to have died.
The Splash screen comes up straight away, but then just sits there for 10-20 minutes, before Fiji loads.

This only occurs when Fiji is loaded for the first time. After re-starting it loads within ~10 seconds.

I've run Fiji through the console using the --debug command, and have included the relevant output below. I have indicated where the hangs occur (~10 minutes each) with a [*] at the start of the line:


C:\FIJI\Fiji.app>ImageJ-win64.exe --debug

C:\FIJI\Fiji.app>JRE not found in 'C:\FIJI\Fiji.app/jre'
JAVA_HOME contains a JRE: 'C:\FIJI\Fiji.app/java/win64/jdk1.6.0_24//jre'
javaw -Xmx12245m -Dpython.cachedir.skip=true -Dplugins.dir=C:\\FIJI\\Fiji.app -X
incgc -XX:PermSize=128m -Djava.class.path=C:\\FIJI\\Fiji.app/jars/imagej-launche
r-3.1.6.jar -Dimagej.dir=C:\\FIJI\\Fiji.app -Dij.dir=C:\\FIJI\\Fiji.app -Dfiji.d
ir=C:\\FIJI\\Fiji.app -Dfiji.defaultLibPath=bin/server/jvm.dll -Dfiji.executable
=C:\\FIJI\\Fiji.app\\ImageJ-win64.exe -Dij.executable=C:\\FIJI\\Fiji.app\\ImageJ
-win64.exe -Djava.library.path=C:\\FIJI\\Fiji.app/lib/win64;C:\\FIJI\\Fiji.app/m
m/win64 -Dsun.java2d.noddraw=true -Dij.debug=true -Dscijava.log.level=debug net.
imagej.launcher.ClassLauncher -ijjarpath jars -ijjarpath plugins net.imagej.Main

Using JAVA_HOME C:\FIJI\Fiji.app/java/win64/jdk1.6.0_24//jre
Opening Java library C:\FIJI\Fiji.app/java/win64/jdk1.6.0_24//jre/bin/server/jvm
.dll
Adding option: -Djava.home=C:\FIJI\Fiji.app/java/win64/jdk1.6.0_24/
ij1.plugin.dirs: null
$HOME/.plugins: C:\Users\amc910\.plugins does not exist
Launching main class net.imagej.Main with parameters []
[*]Class loader = sun.misc.Launcher$AppClassLoader@138d107f
Checking class loader: sun.misc.Launcher$AppClassLoader@138d107f
Checking URL: file:/C:/FIJI/Fiji.app/jars/imagej-launcher-3.1.6.jar
[*]Not Eclipse because first entry is: file:/C:/FIJI/Fiji.app/jars/imagej-launcher-
3.1.6.jar

...log continues after this, but no further hangs and Fiji loads soon after.

If you need any more information please let me know.

Kind regards,
Angus
Comment 1 amc910 2015-10-06 06:33:13 CDT
For clarity the hang occurs ON the line indicated with a [*], i.e. the line 'Class loader = sun.misc.Launcher$AppClassLoader@138d107f' is displayed, and then nothing happens for ~ 10 minutes.

Angus
Comment 2 Curtis Rueden 2015-10-13 10:11:52 CDT
Two things to try:

1) Did you try pressing Ctrl+Pause in the command line window to generate a stack trace?

Note that you may need to pass the "--console" flag to the ImageJ-win64.exe executable in order to make it behave properly on Windows.

When you press Ctrl+Pause in Command Prompt at the hang point, you should see a large dump of information about the active Java threads. That information would be helpful to diagnose the problem.

2) After Fiji finally starts up, check Edit > Options > Misc... for whether "Run single instance listener" is checked. Try unchecking it, restart Fiji, and see if the problem still occurs.

Thanks in advance for following up along these directions.
Comment 3 Curtis Rueden 2015-10-13 11:05:03 CDT
Actually, this is indeed a duplicate of #933. So I'm closing this issue in favor of that one. Please follow up further on issue #933.

*** This bug has been marked as a duplicate of bug 933 ***