Killing abusive tabs

Isn't this the kind of thing an OS is supposed to do FOR YOU?

Note that the crafty fuck was smart to delay running the job so that the user was less likely to notice.

>>51572474
Not necessarily. Some jobs like encoding or compiling have legitimate reason to push the system.

A fucking weabo site does not.

>>51572450
Write a script to check a process having cpu usage >50%, put it on cron, like, every 5 secs... Problem solved.

>>51572513
That's not a reasonable solution. A process, including individual tabs or the browser itself can go over 50% for short periods of time (especially with the js heavy crap web devs like to push).

What I want is something like a browser addon or a daemon that will monitor the tabs and kill anything that runs high on average for a specified period of time.

does something like this exist yet?

>>51572450
If you did this without privilege just do $ ps aux | grep <user>.

Then search your process. If you know its name just do $ killall <process>.

Source : https://panaharjuna.wordpress.com/2009/10/19/kill-process-using-kill-command-under-linuxunix/

>>51572636
>>51572649
This is not stackoverflow

Also your suggestion is useless

File: BPS.jpg (13KB, 275x174px) Image search: [Google]

13KB, 275x174px

>>51572578
maybe customize the script to log the values u get every 5 secs
the revisit these values every "insert time period" and calculate an average.. then decide if this value is bigger than "insert ur threshold value %" if this = true kill the program

>>51572671
Suggesting my comment *may* be useful would imply this website would be too, which is not the case.

>>51572693

Yes. But then I'd have to write it, which I don't want to (hence this post). Also, if you're going that far, might as well use a proper programming language.

Anyway, there will be an issue with false-positives like youtube. I think an addon is the only reasonable way to go. :(

File: tumblr_meu69yUocD1rwjzpqo1_500.gif (115KB, 499x272px) Image search: [Google]

115KB, 499x272px

>>51572737
That, or hooking up to the browsers debugging interface, which sounds significantly more interesting,

>>51572450
>>51572513
>>51572693
>>51572737
https://wiki.archlinux.org/index.php/Cgroups

>>51573339
>https://wiki.archlinux.org/index.php/Cgroups

Leaving false-positive issues aside, cgroups does nothing to remedy the original complaint (gpu thieving tab).