I suspect that there's some memory sharing issues when FF WebGPU api is activated.

@mangeurdenuage
FF is a trainwreck rn. I switched to ungoogled-chromium, uses barely any ram and is very stable.

@dushman My hardware is also failing so it might also be that.

There's no good choice in browsers these day, but I rather use something that isn't made by google.

@mangeurdenuage
As long as it's open source and everything that pings back to google is cut out then I don't mind

@dushman Trisquel removed it from it's repo after being deceived many and many time by diverse types of blobs and functions that shouldn't have been there.
The good thing I can say about ungoogled chromium are the sane browser configuration. But it lacks a few that only FF has, notably about cookie management.

>then I don't mind
From a market share perspective I'd still mind, the issue of having chrome being dominant is that idiot are making "website/apps" only compatible with that, from my perspective chrome is just the new IE.

@mangeurdenuage
Well yeah, I don't like monopolies either. I hope we get another foss browser that can stand up to the competition.

@dushman
>we get another foss browser that can stand up to the competition.
We won't.
There's a need for a massive amount of resource to be able to follow the changes that google constantly does to web standards.
And extremely few people, are willing to finance software freedom.

And outside of just google changes, web browsers are as massive as operating systems these days. Blame browser side software execution for that.

@mangeurdenuage
Yeah, that could definitely be a concern. The modern web is pretty bloated.