In windows, by default, multiple DLLs don't merge their dynamic symbols such that they end up using the same heap like they do on linux. They behave closer to having Bsymoblic enabled everywhere.

Because of this, the current shim in windows only works on chrome.dll and not chrome.exe (maybe this os okay??? how much is actually in chrome.exe?)

It's also unclear how well it handles differentiating between different allocator calls (malloc vs VirtualAlloc vs HeapAlloc, etc etc).

Lastly, the shim was built before the current memory infrastructure meaning it is different from everything else.

Resolve all these bits.