@colon_three what's that

it's xubuntu 16

@squirrel oh shit nevermind

it's a gnome fileindexer that caused me no end of hassle bc it constantly pegged cpu cores and thrashed my drives

@squirrel it wasn't til i ran htop that i realised just what was hemorrhaging resources

@squirrel i think other DEs use it too though, so that might be worth a look

@colon_three tracker: no process found

@squirrel hm

what does htop say when you run it

@colon_three the fucking xscreensaver was running on all 4 cores this whole time somehow ???

i killed it but the lag is still going, i can't tell what's causing it because everything in htop is foreground stuff i'm running that shouldn't cause this

@squirrel ok now that's just fucking weird

but apparently xscreensaver *is* a complete and utter resource hog and i can't think of anything at this stage other than removing the package

@colon_three i like xscreensaver, i just killed the rogue screensaver running

first process in mem_percent is firefox with 36%

second is discord with 7%

i'l just try getting firefox quantum on this piece of shit

@squirrel worth a shot

i should probably try it on mine as well bc chrome is a bit wonky

@colon_three yeah did that and it seems to not be hanging up anymore. guess that was it

@squirrel woot \o/

out of curiosity i checked taskmanager on my ff56 build on windows and it appears to be doing the exact same thing

time to update i guess

@squirrel @colon_three recompiling or retrieving the latest binary package directly from the developer site works, too. the packages (of xscreensaver) supplied by Ubuntu and Debian are usually quite out of date.