Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

When Firefox starts it opens dozens of empty windows

  • 1 réponse
  • 1 a ce problème
  • 3 vues
  • Dernière réponse par quietswan

quietswan
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.

Toutes les réponses (1)

quietswan
quietswan Auteur de la question
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.