-
-
Notifications
You must be signed in to change notification settings - Fork 70
Processing OpenGL renderer core dumping on Raspberry Pi #1087
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I get this same problem with py5 and while investigating I found it also happens in Processing 4.4.1 through the PDE. I initially thought that the problem was caused by setting the native libraries incorrectly. I'd like to understand how this is done in Processing. I am less familiar with the PDE code. Ideally, py5 and Processing pick the native library directory the same way so both get the same results. I looked in the PDE code and I found this:
private void handleNative() {
String variant = Platform.getVariant();
// use the root of the library folder as the default
File nativeLibraryFolder = libraryFolder;
/*
String hostPlatform = Platform.getName();
// see if there's a 'windows', 'macosx', or 'linux' folder
File hostLibrary = new File(libraryFolder, hostPlatform);
if (hostLibrary.exists()) {
nativeLibraryFolder = hostLibrary;
}
*/
// see if there's a {platform}-{arch} folder
File hostLibrary = new File(libraryFolder, variant);
if (hostLibrary.exists()) {
nativeLibraryFolder = hostLibrary;
} else {
// if not found, try the old-style naming
String oldName = newToOld.get(variant);
if (oldName != null) {
hostLibrary = new File(libraryFolder, oldName);
if (hostLibrary.exists()) {
nativeLibraryFolder = hostLibrary;
}
}
}
// save that folder for later use
nativeLibraryPath = nativeLibraryFolder.getAbsolutePath();
} Before digging deeper, am I looking in the right place? I do know that the OpenGL native library stuff changed from how it was done in the past. Now these files are packaged up in Jars, and I note that MacOS now always uses the universal library and I see linux-arm changed to linux-armv6hf. lib/app/resources/core/library:$ ls -1 jogl*natives*
jogl-all-2.5.0-natives-android-aarch64.jar
jogl-all-2.5.0-natives-linux-aarch64.jar
jogl-all-2.5.0-natives-linux-amd64.jar
jogl-all-2.5.0-natives-linux-armv6hf.jar
jogl-all-2.5.0-natives-macosx-universal.jar
jogl-all-2.5.0-natives-windows-amd64.jar But that isn't relevant to the task at hand. This is 64 bit Raspberry pi, which should go to linux-aarch64, same as it was before. If I roll back to the previous native libraries, it still gives the core dump (at least it did with py5). |
Hi @hx2A I just tried 4.4.1 on my Raspberry pi and it works just fine.
Looks like I might be on an older version, could you give me some more details about the install that you are using? |
Really? I would have guessed that I am on the older version. I set this up about a year ago and haven't done much with it. This raspberry pi runs pihole to block ads (which is awesome by the way, highly recommend) To install this I used the raspberry pi image from the official website, then setup pihole with their script. raspberry pi doesn't let you upgrade the distro through the terminal like other distros, it seems. The documentation says to create a new image on a new sd card. |
Okay I'll create fresh SD and install pi hole as test. Do you know which Raspi you have? I have 3b,4b and 5 and tested on 5 earlier |
I tested on a 3B, which has the hardware floating point and (I believe) should be fine with the OpenGL native libraries armv6hf. |
Okay I'll test on 4 and 3 too then |
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
Install Processing on Raspberry pi 64 bit using snap, as per install instructions
Run this Sketch:
snippet
Additional context
No response
Would you like to work on the issue?
I can help test & investigate
The text was updated successfully, but these errors were encountered: