http://bugs.winehq.org/show_bug.cgi?id=27439 --- Comment #14 from Henri Verbeet <hverbeet(a)gmail.com> 2013-04-10 15:04:52 CDT --- I guess I lost track of this one. (In reply to comment #8)
Yes, I was wrong about HeapAlloc!
when crashed in my case:
data = 0x0d3fedb0, start = 0x3f3608da, !!! len = 0x3f0eafe9, !!! buffer->resource.allocatedMemory = 0x053a50d0
Yeah, those start and len values look wrong. In principle you should be able to see a previous call to wined3d_buffer_map() with equivalent arguments in that case, but buffer_add_dirty_area() would probably have filtered those out, so it seems more likely that there's some kind of memory corruption going on. Perhaps a "+seh,+tid,warn+heap,+d3d8,+d3d" log can provide some more information. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.