Firefox

22294 readers

107 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 6 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

Plugin to automatically kill tabs that are stuck at 100% CPU usage (lemmy.ca)

submitted 4 weeks ago by phoenixz@lemmy.ca to c/firefox@lemmy.ml

14 comments fedilink hide all child comments

So I regularly see issues in Firefox where pages from certain websites (Hello amazon.ca!) shoot to 100% CPU utilization and just never stop.

I'm wondering, is there a plugin that could periodically check the FF process list and identify tabs that are misbehaving like this (or in other ways, extreme memory consumption, perhaps?) and perform configurable actions like "Reload page (GET only of course) on tab" or "Kill tab" ?

It would be helpful because I see this issue on a daily basis, regularly to the point where these tabs are causing problems.

I already have "Auto tab discard" that discards unused tabs, but I'd like this as an extra feature, or a separate plugin.

Anyone who knows what could be useful?

you are viewing a single comment's thread
view the rest of the comments

[–] solrize@lemmy.ml 6 points 4 weeks ago (2 children)

This is an interesting idea but Firefox itself should both limit resource consumption and do those sorts of stops. Hmm.

[–] HubertManne@piefed.social 1 points 4 weeks ago (1 children)

this. no tab should be able to use more than like 10% cpu without a popup and the user manually enabling a higher level from a dropdown or something.

[–] phoenixz@lemmy.ca 1 points 3 weeks ago (1 children)

I'd change that to "more than 10% continuously" because any page can shoot to 100% in short bursts for a wide variety of valid reasons.

It's the continuous load that is a problem, so basically 100% for 10 seconds straight would be a problem

[–] HubertManne@piefed.social 1 points 3 weeks ago

see thats the problem. once it has 100% if it don't let it go then anything setup to stop it can't function. You have to have reserve. I mean you could do 90% maybe even 99% but honestly the issue there is it shoots up so fast the stop does not get a chance to launch.

[–] phoenixz@lemmy.ca 1 points 3 weeks ago

You'd think it would, and it somewhat checks when a page becomes unresponsive, but that's it

Amazon pages (yeah, Amazon sucks, I know) typically just start normal and jump into 100% CPU after being open and left alone for an hour, and Firefox is all okay with that.

I'm not