FS#78503 - Firefox 113.0.1 takes minutes to launch. Uses %100 of a single cpu

Attached to Project: Arch Linux
Opened by D T (the_circle) - Saturday, 13 May 2023, 07:40 GMT
Last edited by Toolybird (Toolybird) - Saturday, 13 May 2023, 21:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

# Output of `uname -a`
Linux ecsh61-h2 6.3.1-arch2-1 #1 SMP PREEMPT_DYNAMIC Wed, 10 May 2023 08:54:47 +0000 x86_64 GNU/Linux


installed libraries are in the attachment "pacman_q_output.txt"
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 13 May 2023, 21:40 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments
Comment by D T (the_circle) - Saturday, 13 May 2023, 08:15 GMT
It happened with a very recent update. After running the `firefox` command, it did not launch for minutes and used %100 of a single core during that time. When it finally opened, I pressed "Start New Session" button, then it hanged for minutes again, It is still hanging. But this time, it consumes almost no cpu time. Nothing unusual with ram consumption. I launched firefox with `MOZ_LOG=all:5 MOZ_LOG_FILE=~/fold_tmp/firefox_related/logs1/log_firefox firefox` the log files that been created can be seen in the attachment. All 7 firefox log files are completely empty. And as you can see, there is 4 minute difference between the creation of the first log file and the other 6 log files.
Comment by D T (the_circle) - Saturday, 13 May 2023, 11:08 GMT
seamonkey also takes more than 3 minutes 30 seconds to launch. It is pretty responsive after the launch. I have downloaded seamonkey from
https://www.seamonkey-project.org/releases/
The specific seamonkey download link is
https://archive.mozilla.org/pub/seamonkey/releases/2.53.16/linux-x86_64/en-GB/seamonkey-2.53.16.en-GB.linux-x86_64.tar.bz2

chromium works without any issues on my system.
Comment by Toolybird (Toolybird) - Saturday, 13 May 2023, 21:40 GMT
Thanks, but this doesn't belong in the bug tracker. Please re-read [1] to see how to put together a proper bug report. To solve issues like this your first port of call is always the support channels (Forum/IRC/Mailing Lists/Reddit/etc) to see if anyone can help. If an Arch packaging bug is identified then please come back here with the details. Here is a post in the forum that might be relevant [2]

[1] https://wiki.archlinux.org/title/Bug_reporting_guidelines
[2] https://bbs.archlinux.org/viewtopic.php?id=285713

Loading...