top | item 45102888

(no title)

gorhill | 6 months ago

When trying to diagnose performance or memory issues with a browser, always start with the installed and enabled extensions.

discuss

order

rcfox|6 months ago

These days, I'd say always start with the YouTube tabs.

ambicapter|6 months ago

Youtube is just hopelessly broken on Firefox/Linux anyways. Half the time the home page doesn't even load.

bilbo0s|6 months ago

Yep. Can’t upvote this enough.

Next up would be looking closer at the pages you frequent. I think many people would be surprised at all the ways web apps screw up these days.

All that said, the browsers, as unfair as it may seem, should do better at handling all of the slop that web app and extension developers put out there. It’s sometimes just a whole lot easier to make the browser more bulletproof than it is to make a bajillion JavaScript/python monkeys conscientious and competent.

mdaniel|6 months ago

An alternate between those two endpoints would be to offer better tooling to enable both users and monkeys to identify things contributing to bad outcomes. I don't just mean devtools, either, I mean "oh, it seems this tab is taking up $foo memory because the background image is a 400MB .mp4 and ..." type thing. They went through all the trouble to put AI in the browser, so ask it :-/