I'm curious whether the "new"(ish) segment heap would address some of the author's issues. It's poorly documented, so I can't find a reference explaining what

I'm curious whether the "new"(ish) segment heap would address some of the author's issues. It's poorly documented, so I can't find a reference explaining what it is on MSDN save for a snippet on the page about the app manifests[1]. There's some better third-party "documentation"[2] that gets into some specifics of how it works, but even that is light on the real-world operational details that would be helpful here. Chrome tried it out and found[3] it to be less than suitable due to its increased CPU cost, which might presage what Erik would see if they enabled it. [1] https://docs.microsoft.com/en-us/windows/win32/sbscs/application-manifests#heaptype https://docs.microsoft.com/en-us/windows/win32/sbscs/applica... [2] (PDF warning) https://www.blackhat.com/docs/us-16/materials/us-16-Yason-Windows-10-Segment-Heap-Internals.pdf https://www.blackhat.com/docs/us-16/materials/us-16-Yason-Wi... [3] https://bugs.chromium.org/p/chromium/issues/detail?id=1102281 https://bugs.chromium.org/p/chromium/issues/detail?id=110228...