⚠

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 1089 - Error in Fiji ImageJ java.lang.IllegalArgumentException: invalid range properties
Error in Fiji ImageJ java.lang.IllegalArgumentException: invalid range prop...
Status: NEEDSINFO
Product: Fiji
Classification: Unclassified
Component: Plugins
unspecified
PC Windows
: P4 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2015-06-16 06:35 CDT by Bert Bosche
Modified: 2015-06-16 08:57 CDT
2 users (show)

See Also:
Description Bert Bosche 2015-06-16 06:35:22 CDT 
Dear All,
I have a problem I used the 3D Surface Plot option in Fiji ImageJ, it worked perfectly. Without any obviouse reason, later (30 min) and want to use it again. However, then I got this error message (see below).
I up-dated Java and reinstalled the up-date; and I reinstalled the Fiji program as well, but still I can't use the
3D Surface Plot, the same error comes up any time now.
Could you please help me soon I need that option for a presentation on a conference soon.

(Fiji Is Just) ImageJ 2.0.0-rc-30/1.49u; Java 1.6.0_24 [64-bit]; Windows NT (unknown) 6.2; 43MB of 2993MB (1%)
 
java.lang.IllegalArgumentException: invalid range properties
	at javax.swing.DefaultBoundedRangeModel.<init>(DefaultBoundedRangeModel.java:85)
	at javax.swing.JSlider.<init>(JSlider.java:259)
	at Interactive_3D_Surface_Plot.createSliderVertical(Interactive_3D_Surface_Plot.java:1752)
	at Interactive_3D_Surface_Plot.createSliderPanel2(Interactive_3D_Surface_Plot.java:1702)
	at Interactive_3D_Surface_Plot.createSettingsPanelRight(Interactive_3D_Surface_Plot.java:1343)
	at Interactive_3D_Surface_Plot.createMainPanel(Interactive_3D_Surface_Plot.java:1258)
	at Interactive_3D_Surface_Plot.createGUI(Interactive_3D_Surface_Plot.java:1222)
	at Interactive_3D_Surface_Plot.runApplication(Interactive_3D_Surface_Plot.java:515)
	at Interactive_3D_Surface_Plot.run(Interactive_3D_Surface_Plot.java:438)
	at ij.IJ.runUserPlugIn(IJ.java:199)
	at ij.IJ.runPlugIn(IJ.java:163)
	at ij.Executer.runCommand(Executer.java:132)
	at ij.Executer.run(Executer.java:65)
	at java.lang.Thread.run(Thread.java:662)

Information about your version of Java:

  os.arch => amd64
  os.name => Windows NT (unknown)
  os.version => 6.2
  java.version => 1.6.0_24
  java.vendor => Sun Microsystems Inc.
  java.runtime.name => Java(TM) SE Runtime Environment
  java.runtime.version => 1.6.0_24-b07
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 19.1-b02
  java.vm.vendor => Sun Microsystems Inc.
  java.vm.info => mixed mode
  java.awt.graphicsenv => sun.awt.Win32GraphicsEnvironment
  java.specification.name => Java Platform API Specification
  java.specification.version => 1.6
  sun.cpu.endian => little
  sun.desktop => windows
  file.separator => \

The up-to-date check says: REMIND_LATER

Information relevant to JAVA_HOME related problems:

  JAVA_HOME is set to: C:\Users\Bert\DOCUME~1\FIJI-I~1\Fiji.app/java/win64/jdk1.6.0_24//jre
  imagej.dir => C:\Users\Bert\DOCUME~1\FIJI-I~1\Fiji.app

Information about the version of each plugin:

Activated update sites:
ImageJ: http://update.imagej.net/ (last check:20150613205343)
Fiji: http://fiji.sc/update/ (last check:20150605080752)
Comment 1 Mark Hiner 2015-06-16 08:57:27 CDT 
Hi Bert,

 It looks like this plugin caches slider settings using IJ.prefs. I'm not sure what went wrong with your installation, but I'm assuming some of these settings got mixed up and incompatible slider settings (e.g. a default value outside of the min/max) were cached, and are now being loaded - causing this exception.

 I uploaded a patched Interactive 3D surface plot that prevents invalid slider creation. You can test it with Help > Update Fiji.

Other things to do:

* Edit > Options > Reset...
  - This will reset your stored Prefs, which hopefully will clear out the invalid values that were stored.

* Launch with a newer Java version: http://imagej.net/Frequently_Asked_Questions#On_Windows
  - Since we don't know what caused the invalid values to be stored in the first place, it's worth a try to use a newer Java version to get bug fixes, etc..