I just had my AMD-based machine crash - repeatedly - every time I tried to use Google Maps inside Firefox for longer than a few minutes.

I haven't confirmed, but I strongly assume that either their graphics drivers or something Ubuntu does with Wayland are not fine.

Seems like a Wayland problem to me. Under X, AMD drivers have been nothing but rock solid for years.

To be fair, you have group the perfect combo for initiating a crash, a google product inside firefox inside linux desktop on wayland.

Of these only Linux kernel is the thing that can take down the whole machine.

On a desktop machine, there isn't a huge difference between a kernel and a Wayland crash. Either way I lost all my state and will end up rebooting.

In this specific case, I was unable to get to a console and had actual things to get done so I wasn't going to debug it.

The cutting edge for graphics is all raytracing, and Nvidia still dominates. DLSS3, pathtracing, etc, these are for 'graphics', but heavily dependent on AI post processing, so Nvidia still rules.

So in the gaming market, Nvidia still commands a huge premium. No AMD card can play Cyberpunk on overdrive 4k.

> The cutting edge for graphics is all raytracing, and Nvidia still dominates. DLSS3, pathtracing, etc, these are for 'graphics', but heavily dependent on AI post processing, so Nvidia still rules.

IMHO, unless you have a $1000+ GPU, RayTracing is still not worth the performance hit. I prefer playing at 100+ FPS with RayTracing off, than turning it on and have my frame rate cut in half.