WebGPU

Th- this 157 version of Firefox fixes 38 high impact vulnerabilities, 29 moderate impact, and nine low impact.

Uh, and to give everyone a sense for what, like, the way these feel, what, what, what they look like, uh, among some of those high impact is a use-after-free vulnerability was found in the widget component, a sandbox escape from the DOM, the document object model, in the navigation component, uninitialized memory in storage, sandbox escape in the security, uh, sandboxing component, privilege escalation, uh, due to a use-after-free in their graphics, the WebGPU component, a sandbox escape due to use-after-free in the DOM, incorrect memory boundary conditions in graphics, privilege escalation due to incorrect boundary conditions in graphics.

Uh, th- that's over in the WebGPU component.

A use-after-free in JavaScript, information disclosure in the networking section, another use-after-free in networking, uh, use-after-free in graphics, another one in JavaScript, a sandbox escape due to use-after-free, undefined behavior in the DOM, use-after-free in the DOM.

There's another one of those, and also in storage.

Anyway, if you go into this mode, it will further lock down the accessibility service to prevent these apps, or to try at least to prevent these apps from abusing that service.

It also adds some other features that are similar to Lockdown Mode, like limiting USB access, and it also disables WebGPU, which I'm not super familiar with.

But it also adds some better intrusion logging that will allow researchers to investigate spyware attacks and things like that.

So it's all really good stuff.

Like, that's...

I think, you know, I don't know how to fix that one 'cause I need a browser to test my, my particular world where I'm doing, like, WebGL and WebGPU.

That, that's a, a tougher one to do, like, in a unit test without, like, lying.

[laughs] And be like, "Did it actually draw the thing I expected it to?" Um, but that, that I think, at least for me, if my tests ran faster, that, that does feel like a bottleneck right now, and that one, I think it just extends past, like, the build toolchain into, like, runtime.

I would still revert to Fable for anything like configuring networking DevOps containers and stuff on Linux.

But when it came to anything to do with the web, WebGPU, web APIs, anything to do with Chrome, it's just been trained on much newer data, and it understands even the int8 optimizations of WebGPU, and it was pretty crazy at writing kernels, both, like, on SG Lang on hardware and making websites and also using WebGPU and yeah, the model is, is just an absolute banger.

It's-- It, it, it is that good.

Uh, it, it does everything.

So this is ideal for a standard RTX 3090 or RTX 4080 desktop setup.

But what I find fascinating is that they also include a WebGPU browser deployment that uses a much smaller model, MiniCPM 5 2B, with a tiny 1.56 gigabyte footprint.

Right.

And that runs fully inside a browser sandbox.

Just imagine the crazy stuff.

So Astri's figuring out basically a render engine that's built on top of WebGPU with 3JS.

I mean, these are things I'm not 100% sure of how it's actually done.

But it feels like a very lightweight, very restrictive of size and GPU usage.