⚠

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 90 - Fiji, occasionally , crashes with Segfaults in the JVM
Fiji, occasionally , crashes with Segfaults in the JVM
Status: RESOLVED WONTFIX
Product: Fiji
Classification: Unclassified
Component: Other
unspecified
PC Linux
: P2 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2009-10-12 13:20 CDT by Stephan Saalfeld
Modified: 2009-10-31 21:40 CDT
0 users

See Also:
Description Stephan Saalfeld 2009-10-12 13:20:38 CDT 
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f38b35aa6d4, pid=10411, tid=139878321006928
#
# JRE version: 6.0_16-b01
# Java VM: Java HotSpot(TM) 64-Bit Server VM (14.2-b01 mixed mode linux-amd64 )
# Problematic frame:
# V  [libjvm.so+0x1cc6d4]
#
# An error report file with more information is saved as:
# /home/saalfeld/workspace/fiji/hs_err_pid10411.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted

This happens on a Ubuntu64 Thinkpad and also on another Ubuntu64 Intel machine.  I experienced this bug several times now but so far only when Fiji was launched with the native launcher.  There is no statistical evidence though that this actually means that the launcher is responsible---it's just that it never happened when running Fiji by a direct java call (same JRE, the Fiji-JRE).

hs_err_pid10411.log on personal request, I do not want to post that here.
Comment 1 Albert Cardona 2009-10-31 21:40:49 CDT 
The JVM is not supposed to segfault ever on any kind of byte code.
So this is a JVM bug.