https://bugs.winehq.org/show_bug.cgi?id=48941
--- Comment #4 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Kyle_Katarn from comment #3)
(In reply to Nikolay Sivov from comment #1)
It's true that what we have is incomplete, for example fSpyed is never set, but how do you that Windows is using HeapValidate and when? Also please attach source code for that test case.
Do you need more details ?
Question regarding HeapValidate() still stands. For use case, no, it's clear what breaks - we simply don't return correct flags, with spy or without. Of course there is not reason to do DidAlloc, or SHGetMalloc() in this code, it should simply call CoTaskMemFree(), or ILFree/SHFree() which is the same thing.