http://bugs.winehq.org/show_bug.cgi?id=31684
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #1 from Bruno Jesus 00cpxxx@gmail.com 2012-09-11 19:07:56 CDT --- I guess in this case you could try a WINEDEBUG=warn+heap It will possibly show a HEAP_ValidateInUseArena line, then do WINEDEBUG=warn+heap,+relay and find the call tree that leads to the agressor.
See http://bugs.winehq.org/show_bug.cgi?id=10111#c0 for an example.