http://bugs.winehq.org/show_bug.cgi?id=27674
--- Comment #3 from Henri Verbeet hverbeet@gmail.com 2011-07-03 17:36:55 CDT --- I suppose you could check if there's anything else that tries to use that texture name. The main functions you'd care about are wined3d_texture_bind() and surface_bind(). Something else you may want to check is if there are any calls to wined3d_device_reset() after the cursor texture is created. The cursor texture should probably be deleted in delete_opengl_contexts(). (I.e., I suspect something along the lines of the GL context going away but cursorTexture not being updated, and then later deleting a different texture that happened to end up with the old cursorTexture name.) The software cursor drawing code is pretty hacky though, I'm not all that surprised it has bugs.