Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

When Firefox starts it opens dozens of empty windows

  • 1 odpowiedź
  • 1 osoba ma ten problem
  • 3 wyświetlenia
  • Ostatnia odpowiedź od 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.

Wszystkie odpowiedzi (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.