<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - WarThunder freezes at start, with activated vsync (vblank_mode=2)" href="https://bugs.freedesktop.org/show_bug.cgi?id=102358#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - WarThunder freezes at start, with activated vsync (vblank_mode=2)" href="https://bugs.freedesktop.org/show_bug.cgi?id=102358">bug 102358</a> from <a class="email" href="mailto:thellstrom@vmware.com" title="Thomas Hellström <thellstrom@vmware.com>"> Thomas Hellström</a> <pre>(In reply to haro41 from <a href="show_bug.cgi?id=102358#c11">comment #11</a>) > i applied your patch successful, still the freezes, maybe in average a bit > later now. > > The behavoir changed a bit: > > before patch: > > vblank_mode=2 (default)-> always freezes inside 0..2 minutes runtime, > framerate fix/clamped at 50(as expected) > vblank_mode=0 -> no freezes at all, dynamic, high framerates > LIBGL_DRI3_DISABLE=1 -> no freezes at all, framerate fix at 50 > > > after patch: > > vblank_mode=2 (default)-> always freezes inside 0..2 minutes runtime, > framerate fix/clamped at 100(!!) > vblank_mode=0 -> no freezes at all, dynamic, high framerates > LIBGL_DRI3_DISABLE=1 -> no freezes at all, framerate fix at 50 > > > To be honest, i am not familiar enough with DRM internals to understand what > exactly happens here, but it looks like something is broken in respect to > DRI 3 usage. > > Somehow i think i could be the only one with this freezes and to ensure i am > not wasting your time: > Can you give me a hint, where i should look first to exclude it is something > specific to my system/setup? That's really weird :). Actually I don't think anything's wrong with your setup, but rather that there's a multithreading bug in dri3 or the app. There's no concurrency protection at all in the dri3 client and I'm not sure that's correct. I think you're the only one seeing this possibly perhaps because you're the first to try it with a heavily multithreaded application. Anyway, I'm OK with commenting out the glFinish() wait for swapbuffers until someone has the possibility to debug this thoroughly. Unfortunately WarThunder doesn't run on vmware's svga driver (yet) due to bugs... It would also be good to try to rule out server side radeon dri3 problems. Perhaps by running it on nouveau or intel...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>