http://bugs.winehq.org/show_bug.cgi?id=29236
--- Comment #9 from Henri Verbeet hverbeet@gmail.com 2011-12-18 09:02:13 CST --- (In reply to comment #7)
One observation that may not be related is that the window titlebar disappears when the graphic window initialises in wine 1.3.35, whereas it doesn't do this in wine-1.3.33.
Could be related to bug 29373.
(In reply to comment #8)
Does a 'set texture' cause a call to X_ShmPutImage?
No, wined3d_device_set_texture() just updates the wined3d state. The corresponding GL state changes don't happen until e.g. a draw call happens.
The resource id 0x460000f does correspond to the drawable for the GL context that was destroyed earlier. The one direct call to XShmPutImage() in Wine is at http://source.winehq.org/git/wine.git/blob/HEAD:/dlls/winex11.drv/dib.c#l326.... If that's the call that's failing, it should show up with +bitmap. If not, is there any chance VirtualGL uses XShmPutImage() for e.g. copying data from one GPU to the other?
Are there any other debug channels that might contain useful information?
If you can make it happen with "+seh,+tid,+synchronous,+relay,+wgl,+bitmap,+ddraw,+d3d9,+d3d,+d3d_surface,+d3d_texture" all on that may help. Chances are that that will make it so slow that it will be hard to reproduce though.