Latest Vanadium release adds support for WebAssembly even when JavaScript JIT is disabled.
- Enable support for the DrumBrake WebAssembly interpreter previously exclusive to Microsoft Edge to support WebAssembly when JIT compilation is disabled. JIT compilation is disabled by default in Vanadium with a per-site toggle to opt into it for improved performance that's rarely needed. Vanadium also blocks dynamic code generation via seccomp-bpf in processes other than the per-site renderer sandboxes for sites where the user has enabled JIT compilation. WebAssembly normally depends on JIT compilation and users previously had to enable the per-site JIT toggle for sites requiring it even if the improved performance of JIT compilation wasn't needed. It should no longer be necessary to enable the per-site JIT toggle for compatibility reasons, only if users want to improve the performance of a demanding web application. Certain optional WebAssembly features aren't yet supported by the DrumBrake interpreter but this shouldn't reduce compatibility in practice since dynamic detection with fallback code is already required for broad compatibility.
#GrapheneOS
nostr:nevent1qqs84lmwyuq0svpjdm9ur0yeqw6pu0804e36ufymerlwl3cakwvamzgpr9mhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt9upzpva683gyt7a0nxlfedx648ca0whwm2aql3dezkt9z830k7nsm4leqvzqqqqqqyx7fagg