Yes, all Chromium variants AFAIK.Applies to Javascript optimization disabling in Chrome?
Yes, all Chromium variants AFAIK.Applies to Javascript optimization disabling in Chrome?
I'm not sure,the Chrome doesn't come with "DrumBrake".
No. In the liinked abstract it says,to avoid the vulnerability in Edge.
You must not disable JIT to take advantage of the workaround.
All 23 vulnerabilities have been patched by Microsoft
Offensivecon: Drumbrake adds massive attack surface (applies to Vanadium) - GrapheneOS Discussion Forum[Drumbrake] substantially reduces attack surface compared to the JIT. DrumBrake is an alternative to JIT compilation for WebAssembly. Vanadium isn't adding functionality not present in Chromium but rather is using a more secure and lower attack surface implementation by default. DrumBrake provides a far more secure implementation of WebAssembly compared to having the baseline JIT or all 3 JIT tiers enabled for it. In Vanadium, the JIT toggle is supposed to be a performance vs. security toggle and shouldn't lose functionality such as WebAssembly. ... DrumBrake is clearly the lesser evil by far. DrumBrake is very clearly a more secure approach. That doesn't mean it won't have security vulnerabilities. The point is having fewer vulnerabilities along with being able to have more hardening enabled that's incompatible with JIT compilation. If we didn't have DrumBrake, then the JIT disabled default in Vanadium would become increasingly impractical until the point we had to switch it back to being enabled by default.
DrumBrake was developed to provide a "JIT-less" way to run WebAssembly. It is a bytecode interpreter that allows Chrome to execute Wasm code without needing to compile it into machine code on the fly. This provides two major benefits:
- Security: By avoiding JIT compilation, it reduces the "attack surface" that hackers can use to take control of a process.
- Memory Efficiency: It allows WebAssembly to run on devices with very low memory where a full JIT compiler would be too heavy.
Why is it used?
You’ll mostly see DrumBrake active when you are using Chrome's Enhanced Security Mode (or "Super Duper Secure Mode" in Edge). When you disable the V8 optimizer for extra safety, the browser normally wouldn't be able to run WebAssembly at all. DrumBrake steps in as the "backup engine," allowing sites that rely on Wasm (like Google Meet or certain web games) to keep functioning—albeit more slowly—without the risks of JIT.
Recommend to keep JS optimization on or to turn off?Additionally, Chrome implements DrumBrake according to Gemini.
I've always turned it off in Chrome, Edge and Brave. Browsers work just fine without it.Recommend to keep JS optimization on or to turn off?
I asked this to both Gemini and ChatGPT when you posted the info. Gemini says Chrome uses it while ChatGPT says it doesn't. I gave each other's answer to each other, and they just kept arguing and disagreeing. Both had good logic behind their answers. Since there is no official info on whether Chrome uses DrumBrake or not, I'm not sure who's right and I didn't do any more research by myself.Additionally, Chrome implements DrumBrake according to Gemini.
Speed seems very good to me with JIT disabled but I can't say I've compared them both. And I tend to trust GOS developers' info regarding DrumBrake.Anyway, I am not using Edge's enhanced security mode. For me, sacrificing speed while worrying about JIT vulnerability falls under paranoia.
The comment from GrapheneOS makes it seem like DrumBrake is not present by default in Chromium. They adopted it in their own browser for security benefits.Speed seems very good to me with JIT disabled but I can't say I've compared them both. And I tend to trust GOS developers' info regarding DrumBrake.
You may be right.The comment from GrapheneOS makes it seem like DrumBrake is not present by default in Chromium. They adopted it in their own browser for security benefits.
It's not 100% clear from the comment.
I asked Claude AI to analyze all the browser codes listed in the online table, focusing only on the two most recent versions released.The comment from GrapheneOS makes it seem like DrumBrake is not present by default in Chromium. They adopted it in their own browser for security benefits.
It's not 100% clear from the comment.
No changelog yet
Anyone having trouble with this update not installing?
... and nothing happens later.![]()
Same thing happened with the latest update. I shouldn't have to reboot to finish the update. MS strikes again!No, reboot your computer and try again?
fwiw Version 147.0.3912.98 installed here no reboot needed... Sometimes You Eat the Bear, Sometimes the Bear Eats You...Same thing happened with the latest update. I shouldn't have to reboot to finish the update. MS strikes again!![]()
![]()