iSeekMain crashing on macOS 12.5.1

Alexis Maizel

• August 26, 2022 07:28

Hello! I'm trying to write a plugin for R10.2.6

I have downloaded and installed the R10 PDK  as well as as the JDK v8 (Temurin - Eclipse v1.8).

I can't get any example plugin from the PDK to execute properly. Plugins seem to compile ok, Geneious starts and then everything crashes with the following message: 'ISeekMain quit unexpectedly'.

I have the following trace in the Java console:

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=6673, tid=0x000000000001f807
#
# JRE version: OpenJDK Runtime Environment (8.0_345-b01) (build 1.8.0_345-b01)
# Java VM: OpenJDK 64-Bit Server VM (25.345-b01 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C  0x0000000000000000
#
# 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:
# /Users/maizel/Code/geneious-10.2.6-devkit/examples/GeneiousFiles/hs_err_pid6673.log

I have also tested with Geneious Prime 2022 and the ad'hoc PDK and JDK (v11). Same behaviour: plugin compiles, Geneious launches then immediately crashes along ISeekMain. 

Any hint on how to solve this :-) 

Many thanks in advance.

 

0

• Official comment

  

  Neil Bradley

  • August 30, 2022 02:22

  Hello Alexis,

  Sorry to hear you are having trouble with this. For R10, it is recommended to use an Oracle JDK.

  Our developers have tested both mentioned scenarios (R10.2.6 on Temurin JDK 8 and 2022.2.1 on Temurin JDK 11) in Eclipse on MacOS 12.5.1, and have been unable to replicate your result. This testing was done on an M1 using the x64 versions of the JDKs.

  Is it possible you've been trying to run with some form of coverage (there are several bug reports against Jacoco/OpenJDK similar to your result), or perhaps you are using the aarch64 JDK (Geneious does not support aarch64 currently)?

  Aside from these hints, if you are unable to get it to work, please contact support here, with the hs_err_pidxxxx.log file.

   

   

Please sign in to leave a comment.