⚠

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 186 - Hotspot crash on painting an overlayed image at high magnification
Hotspot crash on painting an overlayed image at high magnification
Status: RESOLVED WORKSFORME
Product: Fiji
Classification: Unclassified
Component: Other
unspecified
PC Linux
: P2 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2010-06-17 16:46 CDT by Stephan Saalfeld
Modified: 2011-04-13 18:34 CDT
0 users

See Also:
Description Stephan Saalfeld 2010-06-17 16:46:13 CDT 
In TrakEM2, image data can be overlayed using Java AWT composites.  This is typically used to blend in a 3d confocal stack over EM data.  By that, the overlayed image might be displayed at very large magnification when viewing the EM data close to 100%.  Doing this, repeatably crashes the whole Fiji with a seg fault in Hotspot.  I am posting this here because I want to know about how is the policy for such Java-related issues---should we post it to Oracle/Sun?  Which JRE are we using, that from Sun?  Thanks for any hint.

My platform: Ubuntu 10.4 64bit Intel, nVidia

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fa8f61b2796, pid=2770, tid=140363535116048
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) 64-Bit Server VM (14.2-b01 mixed mode linux-amd64 )
# Problematic frame:
# C  [libawt.so+0x68796]  IntArgbPreToIntArgbAlphaMaskBlit+0x306
#
# An error report file with more information is saved as:
# /home/saalfeld/Fiji.app/hs_err_pid2770.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted
Comment 1 Johannes Schindelin 2010-06-17 17:25:45 CDT 
We are using (at least if you downloaded Fiji Heidelberg for the test) Sun's Java 1.6.0 Update 20. But your crash report suggests that you are using Update 16. Please use the new "Update Java" button in the Advanced Mode of the Fiji Updater, and try again.

If the problem persists, please raise a bug with Oracle/Sun http://bugs.sun.com/ (and make sure that you say that it is an overlay using the Alpha channel blit).
Comment 2 Stephan Saalfeld 2010-06-17 17:47:03 CDT 
I used the new "Update Java" button in the Advanced Mode of the Fiji
Updater, and tried again.  Same crash whose report suggests that I am using Update
16.  How comes?

Thanks for any help in advance.
Comment 3 Stephan Saalfeld 2010-06-17 17:51:21 CDT 
No---wrong.  Same crash but with Update 20, I mixed up the numbers of JRE and VM...
Comment 4 Johannes Schindelin 2010-06-17 17:54:27 CDT 
Maybe you are still using the obsolete C++-based launcher? In that case, removing java/linux-amd64/jdk1.6.0_16 is a workaround.
Comment 5 Johannes Schindelin 2011-03-23 14:49:46 CDT 
Does this crash still occur?
Comment 6 Johannes Schindelin 2011-04-13 18:34:09 CDT 
Unfortunately, it seems that I am unable to reproduce this issue. If you can reproduce it reliably, please reopen and let me work out the issue on that computer.