ubersheva wrote:DebugGL2.log
Thanks for that dump. It's really strange, though, because the command dump indicates that the default (zero) framebuffer is bound right prior to the
glDrawBuffer call, and if the default framebuffer is bound, then I can't see how
glDrawBuffer(GL_BACK) could possibly fail. Looking at the glprof-gldrawbuffer-state.txt file you attached, it actually seems to indicate that a different framebuffer is bound at the time of that call (it says framebuffer 2 is bound), and that would explain why
glDrawBuffer itself fails, but that's also really weird, since, again, the call just prior to the call to
glDrawBuffer is the command to bind the default framebuffer. I'm almost left wondering if it's some kind of driver bug. I'm not immediately sure what to make of that.
shubla wrote:Logging in with laptop, has some integrated GPU I think. Mesa DRI Intel(R) UHD Graphics (Whiskey Lake 3x8 GT2)
I'm aware of that error, but it happens so exceedingly rarely for me that it's virtually impossible to debug. Are you saying that it happens reliably to you, or was it just something that happened once?
maze wrote:Can we add UI changes into the client rewrite?
Any UI changes are completely independent of the rewrite, and could be done equally well (probably even with the exact same code) in both the old and the new client, so it's totally unrelated to this thread.