Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut

Utas ini telah diarsipkan. Silakan membuat pertanyaan baru jika Anda membutuhkan bantuan.

Firefox will not open a window after booting for @5 minutes. Process in task manager, multiple clicks makes many windows 5 min later. On multiple PCs.

  • 4 balas
  • 1 memiliki masalah ini
  • 26 kunjungan
  • Balasan terakhir oleh jglee5

jglee5
jglee5
more options

This is on multiple machines, all windows based intel processors. Firefox, when launched after boot, will not start for around five minutes. The process is in the task manager, and each new click will make another process, but no window will open until the time has gone by, then all the times you clicked will open that many windows.

I believe there is some sort of startup script running. I run very few addons (I think only adblockplus) and I do not believe that that addon is on one of the computers with the problem.

This, along with the giant memory leak still in the program, seems endemic to any install of Firefox I have done in the past few years. Looking for high level solution, not "reinstall the program," "remove the addons" etc. Technical information on the PCs is irrelevant as it is on multiple PCs of different brands. Thank you.

This is on multiple machines, all windows based intel processors. Firefox, when launched after boot, will not start for around five minutes. The process is in the task manager, and each new click will make another process, but no window will open until the time has gone by, then all the times you clicked will open that many windows. I believe there is some sort of startup script running. I run very few addons (I think only adblockplus) and I do not believe that that addon is on one of the computers with the problem. This, along with the giant memory leak still in the program, seems endemic to any install of Firefox I have done in the past few years. Looking for high level solution, not "reinstall the program," "remove the addons" etc. Technical information on the PCs is irrelevant as it is on multiple PCs of different brands. Thank you.

Semua Balasan (4)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

You appear to be running an older version of Firefox, so will be missing several security and stability updates. I strongly recommend you update to the most recent version of Firefox. You can read more about how to do this here.

jglee5
jglee5 Pemilik pertanyaan
more options

Multiple machines, multiple versions of Firefox. Looking for a high level solution here. This particular box needs formatting in a bad way, so I might grab the latest version of Firefox when I do it, assuming I can work this issue out to my satisfaction, else it might be time for Chrome.

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

I would recommend updating all the devices in question to the latest version of Firefox.

jglee5
jglee5 Pemilik pertanyaan
more options

Thanks for the help, but you're not really getting what I'm after here. Of course one should update to the latest version of the software, and, when I'm motivated to, I shall. However, the answer to this long-running, multiple PC, multiple version of Firefox question should take the form of something like:

"Hi, the problem is that Firefox has a startup script that looks for widgetX* that can be toggled by various Windows Updates. You can either reinstall this Windows update 12345*, or go into startup.cfg* and set line "check_widgetX" to 0 and that will stop the issue."

  • Neither widgetX, update 12345, or startup.cfg actually exist, this is an example.