Firefox getting extrem slow after ca. 30 min

English Applications
1

Since mid of December I have the problem, that firefox more or less freezes after about 30 min of usage. It takes minutes to refresh a site or open a new one (but it is still possible). I’ve already tried to update to the newest version 146, but it didn’t help. The only solution I’ve found so far is killing firefox and starting it again. Than I have an other 30 min of working.
Any ideas, whats going wrong here and where I could start debugging the problem?

2

Maybe start ist without any addons or a new Profile:

firefox --help
3

Does it happen with Firefox in Troubleshoot Mode? https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode#search

Try downloading Firefox from Mozilla. Download, unzip, and run ‘’‘firefox-bin’‘’ from the folder and see if you have the same issue.

Also clear the browser startup cache. see screenshot

startup cache_Screenshot_20240210_022002
startup cache_Screenshot_20240210_0220022093×590 99.4 KB

4

Thanks for your suggestions. I’ll try them later. For now I tried to find the problem via strace. I got following suspicious lines.

close(14</usr/lib64/libogg.so.0.8.5>)   = 0
mprotect(0x7f3f6d75c000, 4096, PROT_READ) = 0
mprotect(0x7f3f6d78a000, 4096, PROT_READ) = 0
mprotect(0x7f3f6d796000, 4096, PROT_READ) = 0
mprotect(0x7f3f6fc0a000, 4096, PROT_READ) = 0
mprotect(0x7f3f6d7a8000, 4096, PROT_READ) = 0
mprotect(0x7f3f6fc11000, 4096, PROT_READ) = 0
mprotect(0x7f3f6fc19000, 4096, PROT_READ) = 0
munmap(0x7f3f6d7aa000, 137543)          = 0
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 14<socket:[3549757]>
connect(14<socket:[3549757]>, {sa_family=AF_UNIX, sun_path="/run/user/1000/:0"}, 20) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden)
close(14<socket:[3549757]>)             = 0
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 14<socket:[3549758]>
connect(14<socket:[3549758]>, {sa_family=AF_UNIX, sun_path=@"/tmp/.X11-unix/X0"}, 20) = 0
getpeername(14<socket:[3549758]>, {sa_family=AF_UNIX, sun_path=@"/tmp/.X11-unix/X0"}, [124 => 20]) = 0

later socket 14 gives a message (“Die Die Ressource ist zur Zeit nicht verfügbar” means “resource temporary not available”):

recvmsg(14<socket:[3549758]>, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1\10\4\0\311\2\0\0\37\0\0\0\0\0\0\0$\v\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 2884
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)

And even later there are constant error messages from socket 14:

recvmsg(14<socket:[3549758]>, {msg_name=NULL, msg_namelen=0, msg_iov[{iov_base="\1\0000\0\0\0\0\0\327\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 192
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)
recvmsg(14<socket:[3549758]>, {msg_namelen=0}, 0) = -1 EAGAIN (Die Ressource ist zur Zeit nicht verfügbar)

Hopefully that helps to tackle the problem

5

Troubleshoot mode and clearing the starup cache didn’t solve the problem :frowning:

6 
connect(14<socket:[3549758]>, {sa_family=AF_UNIX, sun_path=@"/tmp/.X11-unix/X0"}, 20) = 0

looks like the problem is somehow connected to the X Window system

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.