Firefox

21595 readers

37 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 3 days ago by phoenixz@lemmy.ca to c/firefox@lemmy.ml

9 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?

top 9 comments

sorted by: hot top controversial new old

[–] solrize@lemmy.ml 6 points 3 days ago (1 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 3 days ago

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.

[–] HubertManne@piefed.social 3 points 3 days ago

from my experience things like this generally don't work to well. The problem is that once its at 100% the sytem is bogged down so it won't actually kill it till the tab has calmed down and you can interact yourself again. Granted it might still get it before it spikes again so im not saying its without merit. Just warning to temper expectaions if you do find something like that.

[–] msdropbear@friendica.opensocial.space 3 points 3 days ago (1 children)

@phoenixz about:processes

[–] l3ored@piefed.social 1 points 3 days ago (1 children)

Can you close tabs from there or just put them to sleep?

[–] msdropbear@friendica.opensocial.space 1 points 3 days ago

@l3ored you can close them with it. i find it useful for this purpose, though luckily i only rarely have the need. when you hover over any item listed in the table, at the rhs end a cross appears -- click it to end that process, = close the relevant tab. you can sort the table columns by alphabet, memory, or cpu.

[–] Shadow@lemmy.ca 3 points 3 days ago

This feels like a Band-Aid instead of fixing the root problem. I've never seen this happen, maybe you have a bad plugin causing it? Turn off all your plugins or start a new profile, then turn things on one at a time.

[–] merde@sh.itjust.works 2 points 3 days ago

partner uses Vivaldi which has a very practical option to disable background synchronization for all sites and make exceptions for some.

i can't see something similar in firefox/librewolf preferences

[–] l3ored@piefed.social 1 points 3 days ago

Good idea. For me it’s Google Drive and gmail.