FF 36.0 is v. slow to start - more than 60 seconds. MS Win 7.
I installed FF 36.0 yesterday afternoon. Since then FF is a) slow to start - over a minute, b) slow to respond (same delay) when clicking a link in another program such as TBird. I have executed a refresh and cleared all cache and history. Still same problem even asterf numerous exits via the approved mechanism and restarts of Windows 7. THis is becoming annoying and time wasting. I also set the Norton Firewall setting for FF from Auto to Allow. Doesn't help
All Replies (20)
jhjones said
I installed FF 36.0 yesterday afternoon. Since then FF is a) slow to start - over a minute, b) slow to respond (same delay) when clicking a link in another program such as TBird.
Yesterday I also installed windows update KB3006137 - could that be the problem?
I have same issue and I would like to give more details:
Yestarday I have install FF v 36.0, I have Windows 7, i7 CPU, 8gb RAM and SSD drive
It takes 60-80 sec for Firefox to start also I have noticed that when shutdown it will take about same time for process to disappear. I have tried following:
- Uninstalling old version, - Deleting manually folders in Program Files - Deleting profiles both in AppData/Local and AppData/Roaming - Installing new version - Disabling all the plug-ins and extensions - I have tried safe mode. - And even installing new graphic card drivers
And nothing really helped; I also have "Norton Internet Security". I have done the suggested regarding the Norton Firewall, and I have restarted comp, although it seemed that it helped at first start time was shorten to 3 sec.
But then I have noticed that every subsequent turn on/off will make FF starting slower 60-90 sec. I have remembered that same behavior happened before the Norton Firewall tweaks but I was not paying attention. One more thing I have noticed when I get this slow starts CPU fan will immediately start working in higher speed. (even though CPU sometimes does not get over 3%).
Then I have installed “about:startup” plug-in, and I've disabled all the extensions and plug-ins except the one I have just mentioned. Times in the list are in descending order or last measurement is first, times are in milliseconds. As you can see at the beginning time ranges to 50-60 seconds after each FF restart. Then I have restarted Windows time dropped to 3-4 sec for the first two FF start, 3rd one was again slowed down to 61sec. Then I’ve remembered I have additional component called “Trusteer Rapport” I have uninstalled that one and time dropped from 61s to 14-20 sec, again I have done the Win restart and 1st start of FF dropped to 2.5 sec, subsequent start was again in the range from 13 to 30 sec now.
My question is what is so significant about subsequent start of FF ?
firstLoadURI 33815.06 13951 13706 2nd time after restart 2529 1st after restart 15325 14641 14297 19982 After Trusteer Rapport uninstall 61834 3rd after restart 3340 2nd time after restart 4370 1sr after restart 57445 60357 59894 55924 55912 56622 50682
I have also noticed the slow startup since installing v36.0. This is happening on an older WinXP machine and on a laptop running Vista. No other updates have have been done, so the slowness is down to Firefox. Whatever they've done that makes it slow, needs to be undone.
jhjones said
I installed FF 36.0 yesterday afternoon. Since then FF is a) slow to start - over a minute, b) slow to respond (same delay) when clicking a link in another program such as TBird. I have executed a refresh and cleared all cache and history. Still same problem even asterf numerous exits via the approved mechanism and restarts of Windows 7. THis is becoming annoying and time wasting. I also set the Norton Firewall setting for FF from Auto to Allow. Doesn't help
I uninstalled Trusteer Rapport and startup time of 26.0 went down from 90secs to 5
I uninstalled Trusteer Rapport and startup time of 36.0 went down from 90 secs to 5
My bank requires me to have Trusteer installed. Looks like Mozilla and Trusteer need to talk to each other. Looking at my install history: Trusteer on 23/2, Thunderbird on 25/2 and FireFox 36 on 25th February (history since overlaid by total reinstall of FF 36.0).
Modified
I willnot be reinstalling Trusteer till I know there is a solution. Since I uninsstalled it, everythin on my pc is running several times faster than before.
I do not have Trusteer, so this is not my problem. I believe the slow startup is an issue Mozilla need to address. If trusteer is slowing down your system, you should query with your bank whether this is really necessary.
I have a similar problem. Since Firefox updated to 36 , takes ages to start and open links from all other programs (Thunderbird, LibreOffice, Foxit reader). Goes back to normal When Norton Auto-protect is disabled. Everything's OK when I make Google Chrome my default browser. FF in safe mode does not solve the problem. Spent about an hour with Norton remote assistance to no real avail. Uninstalled the French version of FF36 and installed the US version. Does not make any difference either. However I would hate having to use another browser. If anyone has an idea, it will be welcome Thanks
does anyone from Mozilla see these posts, or do we need to raise it as an issue?
Nigel_Cox said
does anyone from Mozilla see these posts, or do we need to raise it as an issue?
Good point does anyone know how to raise an issue ?
Oops - I clicked on 'Problem Solved' due to not using Trusteer. My mistake. It is not solved.
Also - how does one get Mozilla to raise a problem? THis forum took me ages to find in the first place. Mozilla seems very cagey about how to raise a problem
jhjones said
Also - how does one get Mozilla to raise a problem? THis forum took me ages to find in the first place. Mozilla seems very cagey about how to raise a problem
This forum is a lot easier to find and access than previously, although still not glaringly obvious. The old system, (not used it for a couple of years or more) had an option to raise a problem with Mozilla, but I cannot find such an option now. Looks like this is it, where the customers try to find their own solutions, or we just hope that someone from Mozilla is watching. It would be nice if they replied, at least to say, "we're working on it". I'm going to revert to 35.0.1
As I have three PCs, I download the file at each update and install from there to each of the PCs. I keep the last three versions on my hard drive, so reverting is easy. I do the same with Thunderbird.
Its a big file, so can't send it anywhere, sorry.
Found a link, have a browse of this: https://support.mozilla.org/en-US/kb/install-older-version-of-firefox
This page also allows us to report an issue, so I've done that, with a link to this thread. Hopefully someone will fix the issue soon.
Modified
Nigel - thanks, going back to 35.0.1 removed the problem. Startup is as expected and linking from another program (eg email) works quickly too. This is indeed a FF 36.0 problem.
jhjones said
This is indeed a FF 36.0 problem.
I've just installed FF36.0.1 but it doesn't solve the problem. It still takes more than 60 seconds for FF to start. When I click a link Firefox loads and shows as a task manager process and takes up CPU cycles but the window does not appear for more than a minute. And I also have an SSD.
So, back to FF35 I go!
So this morning I'm prompted to update to 36.0.1 Disappointingly, slow startup is not listed as either resolved, or a known issue. It would be nice if someone from Mozilla would have the courtesy to reply on here to either confirm or deny whether they know about this issue, if it is fixed, or if they are working on it. We currently seem to be being ignored, not a good feeling.
I'm now trying to create a bug report, hoping that will get their attention, but it seems I need a new login and password. So this forum and bugzilla don't interact with each other. Why not?
Modified
Is there anyone from FireFox team who can answer this at least so we can know that it has been acknowledged? Nowadays I am using Chrome more than the FireFox because this issue ...
I've installed 36.0.1 on my vista laptop, took 10 seconds to load. I'll try it on the XP desktop later, but looks fixed. Shame they can't post on here.
Update: Now installed 36.0.1 on the XP desktop, seems to be working fine there too. so this issue seems to be fixed.
Modified