search

Syphon / Processing

Syphon Implementation for Processing
Other
137 stars 33 forks source link

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

Closed orsjb closed 1 year ago

orsjb commented 1 year ago

Hello,

I've been very happily using Syphon for Processing since my last post and it has worked without fail. Now, all of a sudden, it started to throw this error. I've re-installed the Syphon library (i.e., deleted the Syphon folder in ~/Documents/Processing/Libraries). Still not working. I'm quite certain that no Mac update was run. It just fell over one day and can't get up again. The same error occurs with any of the Example sketches.

Is this due to an underlying library? I quite urgently need this to run for a live stream and I just need to know if there's a library I can reinstall.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x00007ff806708def, pid=1801, tid=11011
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.8+7 (17.0.8+7) (build 17.0.8+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.8+7 (17.0.8+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-amd64)
# Problematic frame:
# C  [CoreFoundation+0x1cedef]  CFEqual.cold.1+0xe
#
# 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:
# /var/folders/vp/s_91jgz16qq7vnnyhjtzhr_c0000gn/T//hs_err_pid1801.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Could not run the sketch (Target VM failed to initialize).
For more information, read Help → Troubleshooting.
orsjb commented 1 year ago

Update (and indeed I think I did raise this issue a few months ago, but forgot about it). The immediate cause of the problem is plugging in a second HDMI monitor. The immediate workaround is NOT plugging in the HDMI monitor. But I presume you still want to track this as a bug.