KhronosGroup / OpenGL-Registry

OpenGL, OpenGL ES, and OpenGL ES-SC API and Extension Registry
679 stars 274 forks source link

GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT #489

Closed apdw3 closed 2 years ago

apdw3 commented 2 years ago

Over a year ago I reported a bug to the OpenJFX / Open JDK community that appeared in OpenJFX13 and is still apparent in OpenJFX 17.0.1. No action was taken as they could not find any significant changes to the OpenJFX12 HeaderFiles in the port to OpenJFX13.

The issue is not present in OpenJFX11 and OpenJFX 12.

Please see https://bugs.openjdk.java.net/browse/JDK-8258601?jql=key%20%3D%20JDK-8258601 for full details of the bug report.

The error message reported is as follows: Incomplete attachment. (GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT)(FBO - 820) Error creating framebuffer object with TexID 1)

The call stack prior to the error is as follows:

//====
mouseEvent:2591, Scene$ScenePeerListener (javafx.scene)
run:409, GlassViewEventHandler$MouseEventNotification (com.sun.javafx.tk.quantum)
run:299, GlassViewEventHandler$MouseEventNotification (com.sun.javafx.tk.quantum)
doPrivileged:-1, AccessController (java.security)
lambda$handleMouseEvent$2:447, GlassViewEventHandler (com.sun.javafx.tk.quantum)
get:-1, 2067987277 (com.sun.javafx.tk.quantum.GlassViewEventHandler$$Lambda$812)
runWithoutRenderLock:412, QuantumToolkit (com.sun.javafx.tk.quantum)
handleMouseEvent:446, GlassViewEventHandler (com.sun.javafx.tk.quantum)
handleMouseEvent:556, View (com.sun.glass.ui)
notifyMouse:942, View (com.sun.glass.ui)
_runLoop:-1, GtkApplication (com.sun.glass.ui.gtk)
lambda$runLoop$11:277, GtkApplication (com.sun.glass.ui.gtk)
run:-1, 1159114532 (com.sun.glass.ui.gtk.GtkApplication$$Lambda$115)
run:834, Thread (java.lang)
//===

It may be possible for you to track down any hidden issue lurking in the Framebuffer module.

Regards Alan

KhronosWebservices commented 2 years ago

Tranferred this issue to the OpenGL-Registry.

oddhack commented 2 years ago

Sorry, but this isn't an issue we can address - this appears to be either an implementation issue, or a logic error in your code. You might try asking on stackexchange for the latter case.