<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/22/2016 03:11 AM, Alexandre
Julliard wrote:<br>
</div>
<blockquote cite="mid:87d1m6tr2w.fsf@winehq.org" type="cite">
<pre wrap="">Miklós Máté <a class="moz-txt-link-rfc2396E" href="mailto:mtmkls@gmail.com"><mtmkls@gmail.com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">Hmm, you are right. Mesa does set an XCloseDisplay callback to clean
things up for the display connections it encounters. If I use
data->display instead of gdi_display for pglXCreateWindow in line 1358
of opengl.c, the tests pass, and no zombie glx windows remain. I don't
know if I should dare to take responsibility for this change, though,
as I know almost nothing about GDI.
</pre>
</blockquote>
<pre wrap="">If it works then it's the right thing to do.
</pre>
</blockquote>
I did some further testing, and it doesn't work. Mesa glx maintains
its state per-display, and creating a drawable with one display
connection but makecurrent with an other one can lead to bad things.
Unfortunately, wine-csmt likes to do those from separate threads, so
the thread-specific display connections cannot be used instead of
the global gdi_display.<br>
<br>
MM<br>
</body>
</html>