GeezerVison is showing github.com — P3D and P2D Fail on M4 With Tahoe 26.2 · Issue #1422 · processing/processing4
P3D and P2D Fail on M4 With Tahoe 26.2 #1422DescriptionMost appropriate sub-area of Processing 4?
OpenGL
Processing version
4.5.2
Operating system
macOS
Bug description
Rectangle flickers. Video of output is here:
https://www.dropbox.com/scl/fi/nx5pdjvkofi9xfd36cwb0/test.mov?rlkey=iriwzge6w1kdjok35cdqgwfxy&st=hruxsw0g&dl=0
test.mov
Steps to reproduce this
-
Run the source code below on an M4 MacOS system with Processing v.4.5.2.
-
Observe output.
snippet
void setup(){
size(600,600,P3D);
rect(50,50,200,100);
}Additional context
No response
Would you like to work on the issue?
No, I’m just reporting the issue Activityhx2A commented on Feb 8, 2026 I can reproduce this, also on an M4 laptop with Tahoe 26.2. The bug first appeared in Processing 4.5.0. It is not in 4.4.10.
I see the native JOGL jars are the same in 4.4.10 and 4.5.0, so that's not the source of this. They are different in 4.5.2.
I also see that I can make the problem go away by adding an empty draw() function to make it into a non-static Sketch:
This can be used as a workaround until a proper fix is found.
The default draw function is:
void draw() {
finished = true;
}Somehow the finished = true is tripping up the Sketch. I can't see why though. vsquared commented on Feb 8, 2026 ContributorAuthor More actions Adding an empty draw() does stop the flicker.
If I add anything to draw() it erases the rectangle that was coded in setup(). There is no rectangle with this code.
void setup(){
size(400,450,P3D);
rect(50,50,200,100);
}
void draw(){
circle(150,200,40);
}Stefterv commented on Feb 8, 2026 I tried to debug this a bit, setting autoSwapBufferMode to false on GLDrawableHelper from jogl makes it go stable again, so it seems something to do with the swapping buffers.
Also I tried 4.3.4 and it has the same issue hx2A commented on Feb 8, 2026 @Stefterv I'm happy to help investigate and debug this. Reacted by Stef Tervelde Reacted by Raphaël de Courville and Xin Xin SableRaf commented on Jul 14, 2026 @hx2A, just checking in. Have you had a chance to look into this?
I could reproduce this on M1 in Processing 4.5.5.
test.mov
Additionally, when moving that same window to another monitor, the canvas turns completely black.
When adding an empty draw(), moving the sketch window to another monitor turns it default grey.
 hx2A commented on Jul 15, 2026 Sorry to let you down @SableRaf , but I'm over-allocated at the moment and have been so for some time. If someone else is available to work on this and wants it, you can assign it to someone else. If not, I am still willing to try.
Additionally, when moving that same window to another monitor, the canvas turns completely black.
Does your second monitor have the same pixel density as your main display? This bug might be separate from the original one. SableRaf commented on Jul 15, 2026
Does your second monitor have the same pixel density as your main display? This bug might be separate from the original one.
No they're different pixel densities. That's caused other issues before so you might be right.
And no worries at all! I was just checking in. If someone else comes who's interested in this, I'll reassign, otherwise feel free to get to this whenever your schedule allows.
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|
