https://bugs.winehq.org/show_bug.cgi?id=26016
--- Comment #29 from Anastasius Focht focht@gmx.net --- Hello Nikolay,
--- quote --- Maybe I missed something, but how does a private heap help with a corruption? It could be less destructive but if it's not where a real problem is why do we need this workaround? --- quote ---
yes, it doesn't really fix it - until the real cause is found. It reduces the probability of encountering a crash during install time considerably. There is already a high congestion in the heap for small blocks during run of installer, increasing the likelihood of 'collateral damage' by any win32 component.
It's not uncommon for MS installers to rely/make use of undocumented (internal) data structures, in this case setupapi.
Having a separate heap/wrappers might ease the task of isolating the actual set of API which causes the corruption.
Regards