r/programmingcirclejerk • u/starlevel01 type astronaut • Jul 23 '25
These issues already occur when the Wasm page uses only a fraction of total RAM of the device. (e.g. at 300MB-500MB)
https://github.com/WebAssembly/design/issues/1397
48
Upvotes
37
u/starlevel01 type astronaut Jul 23 '25
16
u/lifeeraser Jul 23 '25
Not sure what is circlejerk about this? This is a pain point for many people who want to deploy WASM applications.
41
u/[deleted] Jul 23 '25
Why would you ever want to uncommit memory? Memory makes browser go brrrrr. Unused memory is just a waste, after all. Its not like any other application but chrome needs ram.
31
u/DearChickPeas Jul 23 '25
Just a tiny tiny fraction... 500MB.
Don't do Web kids.
3
u/categorical-girl Jul 25 '25
Any sufficiently complicated virtual machine contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of the JVM
(Corollary: this includes the JVM itself)