How do I fix slow start-up of Firefox 33 on GNOME 3.12+?

In both GNOME 3.12 on Fedora 20 with the rhughes Copr repositiory, and GNOME 3.14 on Fedora 21, and especially on a wireless network, Firefox 33 takes around 20 seconds to start. Changing almost any configuration option in Firefox often causes it to start in the usual one or two seconds the next time, but after that it again goes back to the long start-up time of around 20 seconds. It's not just the first time I start Firefox after booting, which normally takes a few more seconds; it happens every time I start Firefox, even within the same (login) session. This always happens with a wireless (Wi-Fi or mobile broadband) network but almost never with a wired connection. However, on Ubuntu, with the same network configuration, Firefox starts up in the normal way in a few seconds.

I have tried disabling IPv6 in the system's network connection, I have set network.dns.disableIPv6 to true in the Firefox configuration, I have set the home page to blank, unpinned websites from the new tab page, reset Firefox, tried with add-ons and plug-ins disabled, tried safe mode, changed the Firefox profile, and tried with a different user account, all to no avail.

Is there any way to fix this? I do not want to switch to a different browser (I have tried other browsers and they start normally, so it seems to be something with Firefox). I did not have this problem with Firefox 32 and older versions but I don't want to go back to those versions either. I would greatly appreciate any help.

edit retag close merge delete

Try creating a new firefox profile and see if the issue persists: firefox -ProfileManager

( 2014-11-14 08:13:14 -0500 )edit
1

I have done that, as I said in my question ("...changed the Firefox profile..."). No luck.

( 2014-11-14 08:26:45 -0500 )edit

Check the journal to see if there are any error messages. Also try starting ff from the command line in debug mode. Check the changelog between FF32 and 33 to see if there are any changes that might cause this. A number of things could cause it, unfortunately.

( 2014-11-14 09:36:51 -0500 )edit

Yes, a number of things could cause it (bother!); and narrowing it down might require some time. Let me see if I can get down to a "debugging" session.

( 2014-11-15 08:30:21 -0500 )edit

Sort by » oldest newest most voted

in a terminal try firefox -safe-mode

you can use strace firefox to catch bottle neck.

try to install midori,konqueror,qupzilla,chromium,... to compare the networks if you think it's related to the wifi

more

I had tried Safe Mode and other browsers already, as I mentioned in my question. I will try with strace.

( 2014-11-15 08:25:37 -0500 )edit

if you don't care you can delete your ~/.mozilla/firefox directory to erase any configuration and start from new.

( 2014-11-15 12:40:10 -0500 )edit

I had tried posting a comment here but it was rejected by the moderator. I posted an extract from strace at fpaste.org/151222 - I will not make a hyperlink, in case it is rejected again. It shows four 5-second time-outs on socket interfaces, which would account for 20 seconds, but the sockets are opened in non-blocking mode, so I am not sure if they are the cause. Anyway, I don't know if I will be able to keep at this, because I have been spending time on it at the expense of my day-to-day work. Thanks for your help. :)

( 2014-11-19 01:18:51 -0500 )edit

I suggest filing a bug with all the info you've collected. The maintainers might have an idea.

( 2014-11-19 03:00:57 -0500 )edit