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!

Search Support

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.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

When Firefox starts it opens dozens of empty windows

  • 1 eyano
  • 1 eza na nkokoso oyo
  • 3 views
  • Eyano yasuka ya quietswan

more options

If I close Firefox v4.0.1 with a number of tabs open (around 8), then I start Firefox v4.0.1 running again it comes up with one window which has my original tabs loaded, but it also opens over a dozen other new Firefox windows each one of which is blank. I have to manually close down all of these windows. This happens every time Firefox restarts. Clicking on a "restart firefox" link does exactly the same thing as closing Firefox and then starting it again. I feel like I have been hit with one of those old spam web sites before pop up blockers became common. New empty fire fox windows opening all over the place.

If I close Firefox v4.0.1 with a number of tabs open (around 8), then I start Firefox v4.0.1 running again it comes up with one window which has my original tabs loaded, but it also opens over a dozen other new Firefox windows each one of which is blank. I have to manually close down all of these windows. This happens every time Firefox restarts. Clicking on a "restart firefox" link does exactly the same thing as closing Firefox and then starting it again. I feel like I have been hit with one of those old spam web sites before pop up blockers became common. New empty fire fox windows opening all over the place.

All Replies (1)

more options

I noticed that the tags that were automatically added to my question show Firefox 3.6.17. I ended up uninstalling v4.0.1 and then going back to v3.6.17. I did this before reporting the issue. The problem I am reporting happens only on v4.0.1, it is not a v3.6.17 issue.