openjdk team mailing list archive

[Launchpad Bug Tracker <609984@xxxxxxxxxxxxxxxxxx>]

[Expired for openjdk-6 (Ubuntu) because there has been no activity for
60 days.]

** Changed in: openjdk-6 (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.
https://bugs.launchpad.net/bugs/609984

Title:
  java crash - probably during file flush when app killed

Status in “openjdk-6” package in Ubuntu:
  Expired

Bug description:
  a soft kill was sent to a java program launched from eclipse (from a terminal, as eclipse cannot do a soft kill). The programs termination hook flushed an output stream - from the file contents, this appears to be where the error occurred: the stream was not flushed, but the console contained output produced just before the 'flush()' call. It is possible that the programs main thread was writing to the stream at the time?

Eclipse handled the error and produced this in the console:
(needless to say, the program terminated)

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x011e2c36, pid=2214, tid=2470357872
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK Client VM (14.0-b16 mixed mode linux-x86 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu lucid (development branch), package 6b18-1.8-0ubuntu1
# Problematic frame:
# V  [libjvm.so+0x321c36]
#
# An error report file with more information is saved as:
# /home/drevicko/workspace-repast/axelrod-direct/hs_err_pid2214.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
#   https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
#