Edge 144 + Strict security causes WASM memory access out of bounds issues #411
Description
I'm working at Nutrient and we have a WASM PDF Viewer. We started getting reports that Edge 144 + Strict security breaks our WASM binary. I've been debugging a little but couldn't quite find a way to make this work yet.
Easiest way to reproduce is to go to https://www.nutrient.io/demo/hello with Strict security enabled. I'm currently reproducing it with Version 144.0.3719.82 (Official build) (arm64) on macOS 26.2.
The binary built in release (-Os + LTO) crashes with various out of memory/bad alloc crashes. The binary built without optimization and LTO works. -O0 and LTO also works.
Our production version of the binary is compiled with Emscripten 3.1.74, but I also tried with the newest Emscripten version (4.0.23). No difference.
I've tried various combinations, but it seems like as soon as I enable optimizations, things break. I changed the code where the first issue was encountered (a static boost::regex constructor) but then it just moved on to another area of the code (Botan ASN parser).
This WASM build runs perfectly fine without Strict security and also in all other browsers. Help? :)
Edit: I'm aware I'm in the completely wrong repo. I'm not sure how to get this to someone knowledgeable. Sorry for disturbing y'all here!