Hello,
After further investigation, this crash only occurs when I invoke imagej
through ssh (with the "-Y" flag).
If I run imagej within some window manager (e.g. XFCE), everything goes
fine.
As a consequence, this looks more like a problem within openjdk.
Sébastien-
On 04/16/2016 09:55 AM, Sébastien Jodogne wrote:
As a complement, you will find the full log attached to this post.
HTH,
Sébastien-
On Fri, Apr 15, 2016 at 10:27 PM, Sebastien Jodogne <s.jodo...@gmail.com
<mailto:s.jodo...@gmail.com>> wrote:
Package: imagej
Version: 1.50i+dfsg-1
Severity: important
Dear Maintainer,
When I try and run the ImageJ package from Debian Sid, I currently
get the following crash:
>>>>>
jodogne@unstable:~$ rm -rf .imagej
jodogne@unstable:~$ imagej
Open other images in this ImageJ panel as follows:
imagej -p 1 <image1> [<image2> ... <imageN>]
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fe91d03ba8a, pid=1262, tid=140639753193216
#
# JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build
1.8.0_77-Debian-8u77-b03-3+b1-b1)
# Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C [libatk-bridge-2.0.so.0+0x10a8a]
#
# Failed to write core dump. Core dumps have been disabled. To enable
core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/jodogne/hs_err_pid1262.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/usr/bin/imagej: line 427: 1262 Aborted
/usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java -d64 -mx474m -cp
/usr/share/java/ij.jar ij.ImageJ -ijpath /home/jodogne/.imagej -port1
<<<<<
This crash makes the imagej package totally unusable to me.
I have removed and purged all the JRE and JDK packages before making
a fresh installation of imagej, but the crash is still there.
I thank you in advance for taking this problem into consideration!
