processing / processing/processing4

Processing OpenGL renderer core dumping on Raspberry Pi

Open
#1,087 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug linux
Dominant language
Java
Stars
494
Forks
183
Avg merge
4h 39m
Merged PRs (30d)
3

Description

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);
}
  1. 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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the minimal P2D sketch on the reported 64-bit Raspberry Pi environment and inspect the generated hs_err_pid10483.log alongside the libnewt_head.so crash frame. Trace the Java_jogamp_newt_driver_x11_RandR13_getMonitorName0 failure and verify that the sketch starts without a native SIGSEGV on the affected setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, linux, raspberry-pi
Domain
computer-graphics, desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.