3 ms·
I’ve gotten in the habit of killing Firefox before going to bed, the processes seem to run away and peg the CPU periodically throughout the night. It seems to b
by Bnshsysjab 6y ago
I’ve gotten in the habit of killing Firefox before going to bed, the processes seem to run away and peg the CPU periodically throughout the night. It seems to be generally Facebook, but other JS heavy sites have similar issues.
- eitland 6y agoGoogle Calendar has had some serious issues with doi g something weird in the background. At some point Google search results page also would spinn up one core on my machine one or twice a minute if left unattended but last I saw that was years ago. (FWIW I don't use Google search much these days, so it might slip by without me noticing.)
- Bnshsysjab 6y agoI don’t understand why tabs are allowed to mindlessly peg CPU, especially after the wave of crypto miners
- eitland 6y agoThis is beyond me as well but I chalk it up to our entire field being immature, which means there are endless possibilities and endless chaos. IMO background activity should need an extra permission similar to notifications and geolocation. But we need to sort out UX (and start punishing the companies that "misunderstand" GDPR to mean they just need to add another popup) as it is starting to get bad now. BTW, this needs to be fixed across a number of situations. There's no reason why I would want to allow a build tool to access all my projects just because I want to allow it to access one project. (Github and Azure Devops, I'm looking at you)
- distances 6y agoWhy wouldn't you poweroff/hibernate computer for the night? Isn't that just a waste of electricity?
- Bnshsysjab 6y agoDepends on how you look at it, I need to keep state of work things (emacs sessions etc). But compared to my fridge or pretty much any industrial country my computers electricity consumption is near negligible.
- distances 6y agoFair enough, though I'm fairly sure my computer, even when idle, draws more power than my fridge.