[GLTeapot] The teapot is not displayed (GL: Error code $0502)

[Akuji]

Error 'GL: Error code $0502' appears when opening GLTeapot. The teapot is not displayed, changing anything in settings of the app doesn't help.

hrev52612 gcc2

Lenovo T430s

device Display controller (VGA compatible controller, VGA controller) [3|0|0]

vendor 8086: Intel Corporation device 0166: 3rd Gen Core processor Graphics Controller

[X512]

Does it still present? Note that Haiku currently use software rendering and videocard have no effect on OpenGL operation.

[cocobean]

Tested on hrev54790 and R1B2 (hrev54154+123). Reproducible bug.

1. Run '/system/demos/GLTeapot' in Terminal window.
2. Move cursor over GLTeapot's GUI window display.

Result: Should see the error in terminal window. Error only happens during mouse movement over application's window - but not main desktop display.

Seems this is coming from events when reading the mouse cursor position over app display. No major issues with teapot display, or any app functions, and can control teapots (i.e. hold/modify) with mouse.

[cocobean]

GLTeapot application showing teapot display and error code $0502 on Haiku R1B2

[cocobean]

@X512 - GLTeapot display is fine on my system. No issues in application functionality. Debug error info is listed here.

1. Mesa: User Error: GL_INVALID_OPERATION in glReadBuffer(buffer=0x405)
2. GL: Error code $0502

See: ​https://github.com/haiku/haiku/blob/master/src/apps/glteapot/TeapotWindow.cpp

void
TeapotWindow::DirectConnected(direct_buffer_info* info)
{
	// TODO: Direct rendering causes the mouse to flicker due
	// to the lack of a Hardware Cursor, however without
	// it the teapot freezes on mouse move. (bug?)
	#if 1
	if (fObjectView != NULL) {
		fObjectView->DirectConnected(info);
		fObjectView->EnableDirectMode(true);
	}
	#endif
}

void
TeapotWindow::MessageReceived(BMessage* msg)
{
//	msg->PrintToStream();
	switch (msg->what) {
		default:
			BDirectWindow::MessageReceived(msg);
	}
}

[kallisti5]

Please run "GLInfo" from the command line and let us know what it says.

[cocobean]

1. mesa-7.9.2-11* (GCC2, Haiku R1B2 +123)

GUI shows:

Mesa Project, 2.1 Mesa 7.9.2, GLU 1.3, GLUT 5

[kallisti5]

Ah. 32-bit gcc2 image.

I'm pretty sure there were some locking fixes applied to the modern Mesa packages (for x86_64). gcc2 gets an old creaky 7.x version of Mesa from our own fork. Were those locking fixes applied there as well?

[kallisti5]

​https://github.com/haiku/mesa_legacy

vs

​https://gitlab.freedesktop.org/search?group_id=1155&project_id=176&repository_ref=&scope=commits&search=haiku&snippets=false

plus

​https://github.com/haikuports/haikuports/blob/f85fb2d8ddbc31ce149a3395a48ff1cca61c05c9/sys-libs/mesa/patches/mesa-17.1.10.patchset

I see some locking fixes in that patchset (I haven't looked at Mesa for a while obviously :-))

[cocobean]

No issue on hrev54795 x86_64.

Recompiling GLTeapot with 32-bit x86 GCC8 and Mesa 17.1.10 fixed the issue. Seems reasonable for faster GL performance (800 FPS vs 500 FPS).

Fixing Mesa 7.9.2 GL lock/unlock seems reasonable as well.

[cocobean]

GLTeapot on hrev54795 x86_64 w/Mesa 17.1.10 (no errors were generated in terminal)

[cocobean]

Resolved. Please close this ticket. Tested platforms: Haiku R1B2 (+123) x86_gcc2, Haiku hrev55147 x86_64

[X512]

What was the cause? Update to Mesa 20+ fixed issue?

[cocobean]

Cause: GL Lock/unlock issue.

  Mesa: User Error: GL_INVALID_OPERATION in glReadBuffer(buffer=0x405)
  GL: Error code $0502

Result:

1. The GL locking/unlocking was fixed in Mesa 17.1.10 and we moved the GLTeapot app to Mesa 17.1.10 and GCC8. Reviewed again on Haiku hrev55145.
2. GLTeapot is visible to users and works fine.

[pulkomandy]

In Haiku gcc2 we do not use Mesa 17, we use Mesa 7.9.2. So what you say makes no sense.

I will wait for confirmation from original reporter (or lack of reply) before closing, since it seems no one else has reproduced this problem.