Firefox causing 5 sec freezes

brodbar

i was tracking cpu usage via htop so i've noticed that firefox is using 100% of the cpu core so i assume that is the case. I will make sure if it is and update this thread.

brodbar

I can confirm that firefox is the issue. That five exact second freeze is still a mystery tho 😀

[deleted]

brodbar do you have fission enabled? it is known to increase memory usage but will provide more security at the cost of some performance.

brodbar

[deleted] It was just fresh installation of solus, if it isn't built-in it wasn't enabled 😃
brent Yes i had swap setup and i determined the issua via htop. I haven't had any freezes since I switched to Opera; so it might point the issue, i guess 😁
Edit:
Fun fact: I've sent this post with firefox because i am too lazy to login again..

brent

do you have swap set up?
also, don't believe firefox is total blame but you can dial in sharper than gnome system settings with
htop
lsof
iotop, sysstat, and dstat are fasincating input/output & sys monitoring tools, too. A little over my head but I get the picture of the processes that consume and what's consumed and how🙂

I digress: but I fear I have too many cli programs already

brent

brodbar I've had a browser like firefox or other drink up all memory til computer seized/freezed often...when I had 4GB. Is that's what is happening? 4GB?

Irregardless tho--if a new browser cured it then more power to you.

[deleted]

brodbar if it isn't built-in it wasn't enabled

it will soon be enabled by default on firefox 95 or 96. more security is on the way!

Axios

I had that problem with firefox way back on budgie but was away from solus for awhile did updates and all and it stopped not sure if it was a solus update or firefox that cured it or low batteries in the wireless keyboard/mouse?

brent

Axios if it was a solus update or firefox that cured it or low batteries in the wireless keyboard/mouse?

welcome to the "i always forget to right stuff down" club. It did stop for me too. It had to after an update OR when I finally shelled out $$ for another 4GB to go to 8GB.
Anyway you say something very interesting. I always secretly wondered if there were hidden system side effects for having draining batteries in keys/mouse?
I'd get the stuttering when typing thing a lot. Or type a lot real words, wait 5 seconds, then watch them come out unrecognizable words. Minor freezes.
ALL that stopped when I went back to wired everything.
Also while I'm babbling let me run this by you. I always had a suspicion that cheap or damaged dongles did real damage to the system in numerous ways, although I have never positively confirmed this, I still believe it.

Axios

I dont think so much as damage but more like not properly designed computer driver or keyboard firmware most all modern Equipment has some form of active battery control other wise batteries would die to quick.
Example the stuff I worked with years ago would shut off equipment for so long then turn it back on for so long and it would keep repeating till user input then go out of battery save mode. But sometimes it went wacky on wake up hence (mad customer..lol)
Most these combo keyboard/mouse setups the mouse talks to keyboard first not directly to usb dongle. So hey my mouse isnt working change my mouse battery still does not work properly but never change the keyboard battery till typing dies on them. (I change them all if one dies on me then I am safe)
The Voltage range of equipment depends alot on design.
Its always a process of elimination like you said you went wired and it worked and he tried another browser and it worked.

brodbar

It's been a long time but i wanted to check if problem still exists. And yes it is. I've managed to solve problem thanks to some article that i came across, sadly i don't remember which.
Disabling hardware acceleration under the Performance section was the solution.

Edit: Can someone please change the title to be more specific, related to the problem? Maybe "Firefox causes 5 seconds freeze" i don't know.

Staudey

brodbar Good suggestion, and glad to see you've found a solution/workaround. For that reason I've also added the "Solved" tag, even though the underlying cause isn't known (but it might be a hard to track down driver issue).