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 925 - FIJI fails to launch due to a third party plugin
FIJI fails to launch due to a third party plugin
Status: RESOLVED WONTFIX
Product: Fiji
Classification: Unclassified
Component: Plugins
unspecified
Macintosh Mac OS
: P4 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2014-08-31 15:01 CDT by claudio.collinet
Modified: 2014-09-09 10:08 CDT
2 users (show)

See Also:


Attachments
Folder containing the plugin preventing FIJI to launch (73 bytes, text/plain)
2014-09-01 06:17 CDT, claudio.collinet

Description claudio.collinet 2014-08-31 15:01:15 CDT
Dear FIJI developers team,
I just update my version of FIJI on a mac laptop (which was running a version before June 2) and since then FIJI fails to launch. By troubleshooting I figured that a specific third party plugin seems to prevent the launching. Indeed, FIJI launches perfectly well without the plugin in the plugin folder but it fails if I put it back there. Strangely enough I don’t have the same problem on another Win7 platform. Clearly, this is an application that I frequently use for my work. I had to rollback to a pre-June 2nd to be able to work, but ultimately I would like to use the continously maintained release.
If possible I could upload the plugin in question to furter give you details about the problem.
Thanks a lot in advance for your help.
Claudio

Information about your version of Java:

  os.arch => x86_64
  os.name => Mac OS X
  os.version => 10.9.4
  java.version => 1.6.0_65
  java.vendor => Apple Inc.
  java.runtime.name => Java(TM) SE Runtime Environment
  java.runtime.version => 1.6.0_65-b14-462-11M4609
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 20.65-b04-462
  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 => /

The up-to-date check says: REMIND_LATER

Information relevant to JAVA_HOME related problems:

  JAVA_HOME is set to: null
  imagej.dir => /Users/Claudio/Desktop/Fiji 2.0.app

Information about the version of each plugin:

Activated update sites:
ImageJ: http://update.imagej.net/ (last check:20140827132801)
Fiji: http://fiji.sc/update/ (last check:20140829104003)

Files not up-to-date:
  b0c7d6a6 (LOCAL_ONLY) 20081207222839 plugins/Orientation-1.0.1_.jar
  43040da2 (LOCAL_ONLY) 20100322144412 plugins/Perkin_ElmerPan1_2_0.jar
  a3b2176c (LOCAL_ONLY) 20090818132553 plugins/metroloJ_.jar
Comment 1 claudio.collinet 2014-09-01 06:17:57 CDT
Created attachment 212
Folder containing the plugin preventing FIJI to launch

This is the plugin I use that prevents FIJI to launch. I copy the entire folder in the plugin folder.
Best
Claudio
Comment 2 Curtis Rueden 2014-09-09 10:08:43 CDT
That plugin bundles conflicting versions of multiple libraries, including a fat batik jar (lib/batik-all-1.7.jar) and -- more critically -- ImageJ 1.x itself (lib/IJ.jar).

In other words: the packaging of that plugin is incompatible with ImageJ2. I suggest contacting the authors about creating either: A) an ImageJ update site that serves the plugin without conflicting libraries; or failing that: B) a standalone JAR file that you can drop into the plugins folder.

As an aside: in general, it's true that ImageJ2 needs to be more resilient to rogue plugins; some discussion of this fact took place at: https://github.com/scifio/scifio/issues/171. Fundamentally, the ImageJ2 & Updater architecture will need some changes someday to minimize the possibility of rogue/broken/malicious/etc. plugins breaking the entire application. Not a trivial problem, though...