Processing 3.x crashing (no error message) when running on a non-native resolution display in fullscreen()

[SimonBiggsUK]

Description

Processing 3.x crashing (no error message) when running on a USB-C Macbook Pro connected to a non-native resolution display in fullscreen().
Not sure if this is a hardware or software issue. Might be a Java environment problem?

The means I cannot run Processing 3.x applications on a non-native resolution projector with a current model Mac (USB-C) in fullscreen mode.

Expected Behavior

Processing 3.x applications will run fullscreen on secondary non-native resolution displays (video projectors).

Current Behavior

Running any Processing 3.4 application on a Macbook Pro with USB-C outputs crashes when running on a non-native resolution video projector (eg: WXGA running at 1920x1080p) with fullscreen() true. The same applications run fine when any of the following are the case:

• fullscreen() is false.
• The projector is set to its native resolution.
• Running on an older Macbook Pro with Lightning outputs (rather than USB-C).
• Running an application in 2.x.

Note: It is only when an application has fullscreen() active, is running in Processing 3.x and on a Macbook Pro with USB-C outputs connected to a non-native resolution display (via HDMI) that it crashes.

Steps to Reproduce

Run a fullscreen() Processing 3.x app on a USB-C output Mac via HDMI to a non-native resolution video projector.

Your Environment

• Processing version 3.4:
• Macbook Pro 15 inch 2018, MacOS 10.13.6:
• WXGA (1280x800) video projector for display, connected to Mac via HDMI and USB-C adaptor - Projector running non-native resolution at 1920x1080p:

Possible Causes / Solutions

Could be HDMI - try replacing with a 15 pin D-Sub cable and adaptor (multisynch VGA) (have not yet tested - adaptor on order).
Could be Java - try running applications in a different Java emvironment (Java is up to date on the computer so difficult to test).
Could be USB-C - run on non-USB-C hardware (have tried this and applications run fine).
Could be Processing 3.x - run on 2.x (have tried this and applications run fine).

[truedat101]

Question are you running an M1 Macbook ? (the new Macbooks launched in 2020 with the ARM processor?)

[SimonBiggsUK]

No. 2018 i9.

[SimonBiggsUK]

Replacing USB-C-HDMI with USB-C-15 pin D-Sub has fixed the problem. But I still do not understand what the issue is, except that HDMI is a static interface and D-Sub is multisynch. But why should that make a difference?

[benfry]

My best guess would be a weird interaction between Java and OpenGL (JOGL). You could also try the most recent 4.x release to see if it's resolved (it has a newer version of Java, as well as an updated JOGL library).