Processing OpenGL renderer core dumping on Raspberry Pi

Most appropriate sub-area of Processing 4?

Core/Environment/Rendering

Processing version

4.4.1

Operating system

Linux pihole 6.12.25+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux

Steps to reproduce this

1. Install Processing on Raspberry pi 64 bit using snap, as per install instructions

2. Run this Sketch:

void setup() {
  size(200, 200, P2D);
}

void draw() {
  rect(mouseX, mouseY, 10, 10);
}

3. Get core dump:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000007f7c0efc5c, pid=10483, tid=10487
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.14+7 (17.0.14+7) (build 17.0.14+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.14+7 (17.0.14+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, serial gc, linux-aarch64)
# Problematic frame:
# C  [libnewt_head.so+0xfc5c]  Java_jogamp_newt_driver_x11_RandR13_getMonitorName0+0x9c
#
# 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:
# /home/jim/hs_err_pid10483.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).

snippet

void setup() {
  size(200, 200, P2D);
}

void draw() {
  rect(mouseX, mouseY, 10, 10);
}

Additional context

No response

Would you like to work on the issue?

I can help test & investigate

Reproduziere die minimale P2D-Skizze in der gemeldeten 64-bit-Raspberry-Pi-Umgebung und untersuche die generierte hs_err_pid10483.log zusammen mit dem Crash-Frame in libnewt_head.so. Verfolge den Fehler in Java_jogamp_newt_driver_x11_RandR13_getMonitorName0 und überprüfe, dass die Skizze auf dem betroffenen Setup ohne einen nativen SIGSEGV startet.