Fiji fails to start with Java-8 on win32

[John Minter]

I have been successfully running the current release of Fiji with Java 8 on
my desktop Win7-x64 image. I have tried to do this with my win7 32 laptop
with the same custom launcher (a shortcut). In this case the code is:

C:\Apps\Fiji.app.win32\ImageJ-win32.exe -Dpython.cachedir.skip=false
--java-home "C:\Apps\Java32\jdk1.8.0_51" --

The version for Java 1.7.0_79 works fine. The version for Java 1.8.0_51
show the Fiji icon for a moment, then nothing. I have verified all the
paths. Have others seen this? Any suggestions?

If you are wondering, I use the non-standard Java install paths to avoid
spaces so I can use Makefiles to run scripts.

Best Regards,
John Minter

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[ctrueden]

Hi John,

> The version for Java 1.7.0_79 works fine. The version for Java
> 1.8.0_51 show the Fiji icon for a moment, then nothing. I have
> verified all the paths. Have others seen this? Any suggestions?

Rename ImageJ-win32.exe to debug.exe and run again. It will show a console
with more information.

See also:
http://imagej.net/Debugging#Launching_ImageJ_in_debug_mode

Regards,
Curtis

On Tue, Jul 21, 2015 at 8:13 AM, John Minter <[hidden email]> wrote:

> I have been successfully running the current release of Fiji with Java 8 on
> my desktop Win7-x64 image. I have tried to do this with my win7 32 laptop
> with the same custom launcher (a shortcut). In this case the code is:
>
> C:\Apps\Fiji.app.win32\ImageJ-win32.exe -Dpython.cachedir.skip=false
> --java-home "C:\Apps\Java32\jdk1.8.0_51" --
>
> The version for Java 1.7.0_79 works fine. The version for Java 1.8.0_51
> show the Fiji icon for a moment, then nothing. I have verified all the
> paths. Have others seen this? Any suggestions?
>
> If you are wondering, I use the non-standard Java install paths to avoid
> spaces so I can use Makefiles to run scripts.
>
> Best Regards,
> John Minter
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[John Minter]

Thanks, Curtis. This is interesting. Looks like they made Java 8  more
memory intensive... Not sure if I can fix this...

Detected ImageJ2
JRE not found in 'C:\Apps\FIJIAP~1.WIN/jre'
JAVA_HOME contains a JRE: 'C:\Apps\Java32\jdk1.8.0_51/jre'
Available RAM: 2047MB, using 3/4 of that: 1536MB
java -Dpython.cachedir.skip=true -Dplugins.dir=C:\\Apps\\FIJIAP~1.WIN
-Xmx1536m
-Xincgc -XX:PermSize=128m -Dpython.cachedir.skip=false
-Djava.class.path=C:\\App
s\\FIJIAP~1.WIN/jars/imagej-launcher-3.1.6.jar
-Dimagej.dir=C:\\Apps\\FIJIAP~1.W
IN -Dij.dir=C:\\Apps\\FIJIAP~1.WIN -Dfiji.dir=C:\\Apps\\FIJIAP~1.WIN
-Dfiji.defa
ultLibPath=bin/client/jvm.dll
-Dfiji.executable=C:\\Apps\\Fiji.app.win32\\debug.
exe -Dij.executable=C:\\Apps\\Fiji.app.win32\\debug.exe
-Djava.library.path=C:\\
Apps\\FIJIAP~1.WIN/lib/win32;C:\\Apps\\FIJIAP~1.WIN/mm/win32
-Dsun.java2d.noddra
w=true -Dij.debug=true -Dscijava.log.level=debug
net.imagej.launcher.ClassLaunch
er -ijjarpath jars -ijjarpath plugins net.imagej.Main
Using JAVA_HOME C:\Apps\Java32\jdk1.8.0_51/jre
Opening Java library C:\Apps\Java32\jdk1.8.0_51/jre/bin/client/jvm.dll
Java HotSpot(TM) Client VM warning: ignoring option PermSize=128m; support
was removed in 8.0
Java HotSpot(TM) Client VM warning: Using incremental CMS is deprecated and
will likely be removed in a future release
Error occurred during initialization of VM Could not reserve enough space
for 1572864KB object heap

John

On Tue, Jul 21, 2015 at 10:42 AM, Curtis Rueden <[hidden email]> wrote:

> Hi John,
>
> > The version for Java 1.7.0_79 works fine. The version for Java
> > 1.8.0_51 show the Fiji icon for a moment, then nothing. I have
> > verified all the paths. Have others seen this? Any suggestions?
>
> Rename ImageJ-win32.exe to debug.exe and run again. It will show a console
> with more information.
>
> See also:
> http://imagej.net/Debugging#Launching_ImageJ_in_debug_mode
>
> Regards,
> Curtis
>
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[ctrueden]

Hi John,

I have observed for many years that with 32-bit Java on Windows, the upper
limit for heap size can be as low as ~1.3GB. So I don't think this is new
with Java 8.

As a workaround, you should be able to launch with the 64-bit VM, change
the memory setting in Edit > Options > Memory and Threads, then relaunch in
32-bit mode.

Regards,
Curtis

On Tue, Jul 21, 2015 at 10:45 AM, John Minter <[hidden email]> wrote:

> Thanks, Curtis. This is interesting. Looks like they made Java 8  more
> memory intensive... Not sure if I can fix this...
>
> Detected ImageJ2
> JRE not found in 'C:\Apps\FIJIAP~1.WIN/jre'
> JAVA_HOME contains a JRE: 'C:\Apps\Java32\jdk1.8.0_51/jre'
> Available RAM: 2047MB, using 3/4 of that: 1536MB
> java -Dpython.cachedir.skip=true -Dplugins.dir=C:\\Apps\\FIJIAP~1.WIN
> -Xmx1536m
> -Xincgc -XX:PermSize=128m -Dpython.cachedir.skip=false
> -Djava.class.path=C:\\App
> s\\FIJIAP~1.WIN/jars/imagej-launcher-3.1.6.jar
> -Dimagej.dir=C:\\Apps\\FIJIAP~1.W
> IN -Dij.dir=C:\\Apps\\FIJIAP~1.WIN -Dfiji.dir=C:\\Apps\\FIJIAP~1.WIN
> -Dfiji.defa
> ultLibPath=bin/client/jvm.dll
> -Dfiji.executable=C:\\Apps\\Fiji.app.win32\\debug.
> exe -Dij.executable=C:\\Apps\\Fiji.app.win32\\debug.exe
> -Djava.library.path=C:\\
> Apps\\FIJIAP~1.WIN/lib/win32;C:\\Apps\\FIJIAP~1.WIN/mm/win32
> -Dsun.java2d.noddra
> w=true -Dij.debug=true -Dscijava.log.level=debug
> net.imagej.launcher.ClassLaunch
> er -ijjarpath jars -ijjarpath plugins net.imagej.Main
> Using JAVA_HOME C:\Apps\Java32\jdk1.8.0_51/jre
> Opening Java library C:\Apps\Java32\jdk1.8.0_51/jre/bin/client/jvm.dll
> Java HotSpot(TM) Client VM warning: ignoring option PermSize=128m; support
> was removed in 8.0
> Java HotSpot(TM) Client VM warning: Using incremental CMS is deprecated and
> will likely be removed in a future release
> Error occurred during initialization of VM Could not reserve enough space
> for 1572864KB object heap
>
> John
>
> On Tue, Jul 21, 2015 at 10:42 AM, Curtis Rueden <[hidden email]> wrote:
>
> > Hi John,
> >
> > > The version for Java 1.7.0_79 works fine. The version for Java
> > > 1.8.0_51 show the Fiji icon for a moment, then nothing. I have
> > > verified all the paths. Have others seen this? Any suggestions?
> >
> > Rename ImageJ-win32.exe to debug.exe and run again. It will show a
> console
> > with more information.
> >
> > See also:
> > http://imagej.net/Debugging#Launching_ImageJ_in_debug_mode
> >
> > Regards,
> > Curtis
> >
> >
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

[John Minter]

Thanks again, Curtis. I did this with the 32 bit Java 7 VM. I was able to
go up as high as 1100m and get things to work with Java-8, Java-7 would run
with 1200. I think I'll back up a working ImageJ.cfg file...

Best regards,
John

On Tue, Jul 21, 2015 at 11:49 AM, Curtis Rueden <[hidden email]> wrote:

> Hi John,
>
> I have observed for many years that with 32-bit Java on Windows, the upper
> limit for heap size can be as low as ~1.3GB. So I don't think this is new
> with Java 8.
>
> As a workaround, you should be able to launch with the 64-bit VM, change
> the memory setting in Edit > Options > Memory and Threads, then relaunch in
> 32-bit mode.
>
> Regards,
> Curtis
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html