Some repeated errors showing up in a debug context.

Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.

If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.

Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is ON
[img] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Some repeated errors showing up in a debug context.

Re: Some repeated errors showing up in a debug context.

by Rachael » Sat Aug 27, 2022 12:34 am

It's fine, this can be moved if need be, but for now I think this is the right place.

Some repeated errors showing up in a debug context.

by KynikossDragonn » Sat Aug 27, 2022 12:09 am

I was in the middle of debugging something else entirely but was curious to run GZDoom in a MESA_DEBUG="context" and I pretty much get this error repeating every frame:

Code: Select all

Mesa: User error: GL_INVALID_OPERATION in glUnmapBuffer(buffer is not mapped)
I also get a lot of these during startup:

Code: Select all

Mesa: User error: GL_INVALID_OPERATION in glGetProgramBinary(driver supports zero binary formats)
Naturally these warnings won't print unless you actually create a debug context, but GZDoom shouldn't really be user erroring every frame like this should it? Isn't that bad for performance? (atleast in OpenGL)

For reference I'm running on Mesa 22.1.7 and a Intel Iris Pro 580.

Sorry if I shouldn't be posting this here, I'm not sure if this should be in "Technical Issues" or here in the OpenGL Renderer Bugs subforum...

Top