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

Replies (7)

Zaikaboy's avatar
Zaikaboy 2 months ago
This last week has seen my bank app fail. It's something I can live with but was wondering if its something the bank has done or Graphene? Any ideas. I know I'm being a little vague
Zaikaboy's avatar
Zaikaboy 2 months ago
I figured. I called them twice, they reset it twice, it worked for a few hours and then didn't. Not once did they question my equipment (ooh er). I am never going back. Graphene has been my daily for 3 years and it feels hood
Vanadium has a built in content blocker (Vanadium Config is the filters). It isn't as powerful as something like Brave's, however.
Billy Bapparoo's avatar
Billy Bapparoo 2 months ago
Any reason why the web search option does not appear in incognito mode, in the selected word popup?