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 98 - "Images to Stack" creates an error message
"Images to Stack" creates an error message
Status: RESOLVED FIXED
Product: Fiji
Classification: Unclassified
Component: ImageJ1
unspecified
Macintosh Mac OS
: P4 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2009-11-04 21:29 CST by Scott DeBoer
Modified: 2010-02-03 17:20 CST
1 user (show)

See Also:

Description Scott DeBoer 2009-11-04 21:29:48 CST
When I have multiple .tif files open and try to use "Images to Stack," I often get the following error message in a window titled "Exception:"  

java.lang.NullPointerException
	at ij.plugin.ImagesToStack.convertImagesToStack(ImagesToStack.java:115)
	at ij.plugin.ImagesToStack.run(ImagesToStack.java:30)
	at ij.IJ.runPlugIn(IJ.java:156)
	at ij.Executer.runCommand(Executer.java:145)
	at ij.Executer.run(Executer.java:76)
	at java.lang.Thread.run(Thread.java:637)

If I retry a couple of times, it will eventually work, but the error happens about 2 out of every 3 tries. I am using the Fiji build of ImageJ version ImageJA 1.43h.

Thanks!

Information about your version of Java - this information is useful for the Fiji developers:
  os.arch => x86_64
  os.name => Mac OS X
  os.version => 10.6.1
  java.version => 1.6.0_15
  java.vendor => Apple Inc.
  java.runtime.name => Java(TM) SE Runtime Environment
  java.runtime.version => 1.6.0_15-b03-219
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 14.1-b02-90
  java.vm.vendor => Apple Inc.
  java.vm.info => mixed mode
  java.awt.graphicsenv => apple.awt.CGraphicsEnvironment
  java.specification.name => Java Platform API Specification
  java.specification.version => 1.6
  sun.cpu.endian => little
  sun.desktop => null
  file.separator => /
Comment 1 Johannes Schindelin 2009-11-12 02:25:33 CST
Could you please update Fiji and run it again? It appears to me that Wayne fixed this issue in 1.43k.
Comment 2 Johannes Schindelin 2010-02-03 17:20:02 CST
I will just assume that it has been fixed.