Hey Google, have you considered unrestricting issue 378017037 so that everyone on Asahi seeing everything Chromium crash due to another 16K page issue can actually find the bug instead of wondering if they're the first to notice?
This clearly isn't a security issue (or you'd have fixed it already, and besides, it would be incredibly bad form to hide a security issue from the users who reported it in the first place, since it was not reported as a security issue), so I can only assume you restricted it to annoy us or pretend your browser isn't broken or something.
(This is worked around on Fedora by reverting the offending Chromium change, but it affects every other distro and Chromium-based browser and app updating beyond 131.)
https://social.treehouse.systems/@marcan/113656361610223289
https://issues.chromium.org/issues/378017037
https://chromium-review.googlesource.com/c/v8/v8/+/5864909
@marcan looks like just a flag change to do page decommitting - seems entirely plausible that it could have acquired a 4k page assumption somewhere (not from knowledge of chrome, just based on […]
@marcan
... component is set to security relevant and all bugs in there are private by default and 'Access' can't be changed to override that.
[…]
@marcan I have found in general that chromium on Linux just isn’t as polished compared to windows. I use Firefox, just out of the fact that it’s the only functional, reliable browser I have, […]
@marcan I get an Access is denied to this issue message upon clicking that first link.
EDIT: Not familiar with that platform apologies.
────