Exported Application broken in 4.0 beta 1 on macOS when using P2D or P3D

[processing-bot]

Created by: philipp-lehmann

Description

When opening an exported application, it immediately quits and MacOS displays an alert saying that the application "quit unexpectedly".

Previous Bug Report

This has been an issue a while back (processing/processing#5983), so maybe its my environment.
However I tried a clean new installation with a very simple sketch and couldn't export a functional app.

Steps to Reproduce

• Downloaded the beta
• Created a test sketch
• Exported the app

Environment

• Processing version: 4.0b
• Operating System and OS version: MacOS Big Sur 11.5.1

My Test Sketch

float rX = 0.0;
float rY = 0.0;

void setup() {
  size(400,400, P3D);
  frameRate(30); // Calling frameRate could help...
  rectMode(CENTER);
}

void draw() {
  background(255);
  translate(width/2, height/2);
  rotateX(rX += 0.005);
  rotateY(rY += 0.01);
  rect(0,0,200,200); 
}

The error messages

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x00007fff201fa25d, pid=18786, tid=12547
#
# JRE version: OpenJDK Runtime Environment Temurin-11.0.12+7 (11.0.12+7) (build 11.0.12+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.12+7 (11.0.12+7, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)
# Problematic frame:
# C  [libdispatch.dylib+0x525d]  _dispatch_assert_queue_fail+0x63
#
# 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/Philipp/hs_err_pid18786.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.

[processing-bot]

Created by: codeanticode

Confirming that it affects my MacOS Big Sur machine (m1 macbook air). I'm attaching the full error log.

hs_err_pid99767.log

[processing-bot]

Created by: benfry

Does that mean you're looking into it?

Might be Java 11.0.12 versus 11.0.11, since it's crashing inside the JVM. We should also see if there are any JOGL reports/updates for this.

[processing-bot]

Created by: codeanticode

I'll look into it on the m1 macbook, and will update as I find more.

[processing-bot]

Created by: codeanticode

This error in the log seems telling:

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: Assertion failed: Block was expected to execute on queue [com.apple.main-thread]
abort() called

@benfry could it be that the application is not running on the correct thread when exported?

[processing-bot]

Created by: sampottinger

Sorry @philipp-lehmann just confirming this was happening in 3 as well? Digging into the jogl bugs, the only thing that stood out was https://jogamp.org/bugzilla/show_bug.cgi?id=1398 but I'm guessing it's something with launch4j and a fork.

[processing-bot]

Created by: sampottinger

Including or excluding the runtime does not help. Unfortunately 11.0.11 doesn't have a release on adoptium. :-/

[processing-bot]

Created by: philipp-lehmann

With 3.5.4 I was able to export P3D applications. However on M1 Macs they only showed a gray screen, as described here: https://discourse.processing.org/t/problems-with-p2d-and-p3d-renderers-with-new-apple-m1-processor/27287

Edit: This still could be this issue? processing/processing#5983

[processing-bot]

Created by: philipp-lehmann

Would it theoretically be possible to include a different jre, optimized for the m1 architecture, for the exported application?
For example this https://www.azul.com/downloads/?version=java-11-lts&os=macos&architecture=arm-64-bit&package=jdk

Or is this the wrong approach?

Idea is from here:
https://stackoverflow.com/a/64940420/3611146

[processing-bot]

Created by: REAS

When exporting with "Embed Java" received this in the command line:
2021-09-10 12:09:39.564 debug_launch[36155:1213366] NSString *findJavaDylib(NSString *, _Bool, _Bool, _Bool, _Bool) Searching for a JRE.
and it looked like it was stuck there

[processing-bot]

Created by: REAS

When exporting without embedding Java, this was reported on the command line, which look like i need to update the Java version locally, but nothing is reported unless it's opened through the command line:

2021-09-10 12:07:48.737 debug_launch[36128:1212132] NSString *findJavaDylib(NSString *, _Bool, _Bool, _Bool, _Bool) Searching for a JRE.
2021-09-10 12:07:48.954 debug_launch[36128:1212170] NSString *findJavaDylib(NSString *, _Bool, _Bool, _Bool, _Bool) Searching for a JRE.
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: debug_launch has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
	at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:601)

[processing-bot]

Created by: matejsemancik

I just came across this issue while trying to solve this exact error in my application builds.

The issue started to appear with Azul OpenJDK to 11.0.12. I downgraded to 11.0.11 and issue went away.
I'm on macOS Big Sur 11.3 and I run Processing using Gradle, so my use-case was a little bit different. Same error, though.

[processing-bot]

Created by: philipp-lehmann

Thats something, how did you tell your exported application which version of the JDK to use?

[processing-bot]

Created by: matejsemancik

Well, since I use the Gradle build system, it's pretty straightforward. I just set the $JAVA_HOME environment variable to directory where my JDK is installed. Unfortunately I cannot tell if the same would work for exporting applications using the Processing IDE.

[processing-bot]

Created by: benfry

Would it theoretically be possible to include a different jre, optimized for the m1 architecture, for the exported application? For example this azul.com/downloads/?version=java-11-lts&os=macos&architecture=arm-64-bit&package=jdk

Or is this the wrong approach?

Idea is from here: stackoverflow.com/a/64940420/3611146

Not that simple; longer explanation here: #128 (comment)

[processing-bot]

Created by: benfry

When exporting without embedding Java, this was reported on the command line, which look like i need to update the Java version locally, but nothing is reported unless it's opened through the command line:

2021-09-10 12:07:48.737 debug_launch[36128:1212132] NSString *findJavaDylib(NSString *, _Bool, _Bool, _Bool, _Bool) Searching for a JRE.
2021-09-10 12:07:48.954 debug_launch[36128:1212170] NSString *findJavaDylib(NSString *, _Bool, _Bool, _Bool, _Bool) Searching for a JRE.
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: debug_launch has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

The UnsupportedClassVersionError is the clue here, it means that there isn't another Java 11 installed on the system (explained in the Export dialog), and it's trying to run the application with Java 8 or something else that you have installed.