Hi Sebastien, On Mon, Apr 18, 2016 at 10:13:15AM +0200, Sebastien Jodogne wrote: > 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.
Thanks for this additional information. Could you possibly verify this by starting some other openjdk based application? At least I can confirm that if I start imagej on a remote host via ssh I also get: $ imagej *.jpg 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=0x00007f2a63ddba8a, pid=6325, tid=139821744850688 # # 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/andreas/hs_err_pid6325.log So this seems to be reproducible at least. Kind regards Andreas. -- http://fam-tille.de