Hello,
Thanks everyone's help, sorry for delay, I was blocked by something else. I've created http://bugs.winehq.org/show_bug.cgi?id=34125 to track down this bug.
On Fri, Jul 19, 2013 at 10:06 PM, Henri Verbeet hverbeet@gmail.com wrote:
Well, it sounds a bit like some form of memory corruption. Sometimes WINEDEBUG=warn+heap helps with tracking those down.
Thanks Henri, warn+heap doesn't show warning, I've attached to Bug 34125, it shows some HeapSetInformation calls, I don't know if it harms.
Also, I don't suppose the d3d9 object was already destroyed earlier?
By reading +d3d9 log, I believe the d3d9 object was not destroyed earlier.