We updated to Spine 3.8.59 and we also updated Spine Runtime for Unity, and now we are re-exporting all Spine assets because of the breaking change (Old projects must be exported with Spine 3.8.20+ to be compatible with the 3.8 Spine runtimes.).

But our automated pipeline

/Applications/Spine/Spine.app/Contents/MacOS/Spine -i "$INPUTFILE" -o "$OUTPUTPATH" -e "$EXPORTFILE"

does not always complete, it sometimes works OK for multiple files but then a fatal error appears. When we try again with that spine file that crashed earlier, it might work OK now.

Error listing is following:

#

A fatal error has been detected by the Java Runtime Environment:

#

SIGILL (0x4) at pc=0x00007fff2d30ba67, pid=9970, tid=775

#

JRE version: OpenJDK Runtime Environment (10.0.2+13) (build 10.0.2+13)

Java VM: OpenJDK 64-Bit Server VM (10.0.2+13, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)

Problematic frame:

C [AppKit+0x41ea67] -[NSApplication _crashOnException:]+0x6d

#

No core dump will be written. 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/someone/someproject/hs_err_pid9970.log

#

If you would like to submit a bug report, please visit:

http://www.azulsystems.com/support/

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

#

I can send the hs_err_pid9970.log file to you via email if you need it