On Thu, 12 Dec 2024 at 21:02, Andres Salomon <dilin...@queued.net> wrote: > ... > Chromium's generally not very good with non-4k page sizes; we're > carrying an allocator patch that we had to add due to hitting asserts() > for 64k pages. Sadly, both the bug report and screenshot are locked down > (thanks google 🙄), so I can't see why they made that > decommit-pooled-pages change. >
>From the history, it appears that this was enabled for better memory efficiency on WIndows. When running chromium in the debugger, I hit a trap in that code, and so I suspect there is some assert() hitting as well, likely due to decommit logic using a fixed 4k page size. It is surprising that this doesn't occur on PPC, but as Tim says, this might simply be due to the lack of memory pressure.
