https://bugs.winehq.org/show_bug.cgi?id=48700
--- Comment #11 from Paul Gofman gofmanp@gmail.com --- (In reply to yaogen from comment #7)
Wasn't aware of the same glitch on Windows.
Please don’t get me wrong, there is no same glitch on Windows I could reproduce if to run the game normally. There are special means how you can trigger that behaviour on Windows and I described that details for an indication that the mentioned use after free is unlikely originates from some Wine code or triggered by some Wine code. Looks like it works on Windows (without forcing the use of debug heap in some way) because the consequent allocations happen not to touch the freed memory block long enough. That’s impossible with debug heap as it intentionally fills the memory with special values on free. Wine does not clear the freed memory but heap allocation algorithm is different and it may result in memory being overwritten sooner.