Bug 104 – Ragular Crash after closing images

Bug 104 - Ragular Crash after closing images


Summary:	Ragular Crash after closing images

Status:	RESOLVED WORKSFORME

Product:	Fiji
Classification:	Unclassified
Component:	Plugins
Version:	unspecified
Hardware:	Macintosh Mac OS

Importance:	P4 normal
Assigned To:	ImageJ Bugs Mailing List

URL:

Depends on:
Blocks:

Reported:	2009-11-16 12:03 CST by ch-n
Modified:	2011-04-23 10:14 CDT
CC List:	1 user (show)

See Also:

Attachments
Crashlog of ImageJ64 (68.01 KB, text/plain) 2009-11-17 12:47 CST, ch-n

Description ch-n 2009-11-16 12:03:30 CST

Start Fiji, open an image/image series, close it. The menubar will only have the "fiji" option (no file, edit etc...).
Click on the main Fiji window and it crashes instantly

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.5.8
  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-226
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 14.1-b02-92
  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 ch-n 2009-11-16 12:04:10 CST

edit: close "it" = close the image, not the main fiji

Comment 2 ch-n 2009-11-16 14:36:21 CST

It now crashes more or less constantly, without an appearant reason or anything, I updated fiji today, including the main package and never experienced anything similar before. Nothing else was changed on the system, everything else works fine.

Some way to downgrade imageJ via the upgrader would be nice...

Comment 3 ch-n 2009-11-16 14:49:37 CST

another status update: it seems to happen ONLY on the tiffs generated by a new beta of the software for the LEICA SP5 microscope, these also crash both, newer and older fiji releases.
Other images work fine in both, the old and the updated fiji and cause no crashes. I have no idea what the cause of this is, but will try to find out more.

Comment 4 Greg Jefferis 2009-11-16 15:01:26 CST

How are the Leica TIFFs being opened (Core ImageJ, LOCI plugins, another Leica Import plugin)?

Greg.

Comment 5 ch-n 2009-11-16 15:03:23 CST

normal imageJ or LOCI, however it doesn't matter, it still crashes

Comment 6 ch-n 2009-11-17 11:56:49 CST

Crashes can be reproduced in the current version of ImageJ and ImageJ64. Importing a sequence and then trying to adjust brightness/contrast results in a crash most of the time, brightness/contrast window opens with no histogram, it stalls for roughly 2 seconds and then crashes.

Comment 7 Johannes Schindelin 2009-11-17 12:31:50 CST

Maybe Console (in Finder, Go to Utilities) has some valuable information?

Comment 8 ch-n 2009-11-17 12:47:38 CST

Created attachment 8
Crashlog of ImageJ64

Comment 9 ch-n 2009-11-17 12:48:34 CST

Even easier, I can just tell it to give me the crashlog... should've thought of that earlier.
Anyway, it's attached now

Comment 10 ch-n 2009-11-17 12:56:55 CST

(In reply to comment #9)
> Even easier, I can just tell it to give me the crashlog... should've thought of
> that earlier.
> Anyway, it's attached now
> 
edit: forgot to mention, it's the crashlog of a normal ImageJ64, fiji is
running some calculations which I can't interrupt at the moment

Comment 11 Jean-Yves Tinevez 2009-11-18 16:57:05 CST

Could you post 2 examples of faulty images and NON faulty images somewhere? Also, if if someone could inform or confirm this bug on a non-mac platform....

Comment 12 ch-n 2009-11-18 17:07:08 CST

I'm waiting for leica to reply to me on this since there's an NDA involved... Meanwhile I was not able to reproduce this bug using windows or linux, so it seems to be mac-specific. I'll try to see whether I can further narrow it down.

Comment 13 Johannes Schindelin 2011-03-23 12:23:04 CDT

I fear we are stuck on this, so I tend towards closing this with a "worksforme" status. Objections?