Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Firefox very slow startup since 26.0

  • 2 përgjigje
  • 3 e kanë hasur këtë problem
  • 4 parje
  • Përgjigjja më e re nga lucas_iv

more options

Since 26.0 firefox takes 20-25sec to open on my very fast PC (win7sp1x64 i7-3930k, 32gb ram, ssd, tried clean os reinstall). Within that time there is absolutely none CPU or disk activity, firefox.exe consumes 0% cpu and just waits something. After that it opens and work as before, no problem at all.

I tried to investigate it and found some dependence on firewall settings. I use windows firewall (adding rules in advanced interface manually) and I have two rules for firefox.exe allowing all TCP and UDP outgoing traffic. When I delete these rules and create one which allows ANY traffic for all apps, firefox opens up instantly. Why that happens? What traffic firefox wants to send if it is not TCP or UDP, and why it hangs if firewall denies such unwanted traffic?

Since 26.0 firefox takes 20-25sec to open on my very fast PC (win7sp1x64 i7-3930k, 32gb ram, ssd, tried clean os reinstall). Within that time there is absolutely none CPU or disk activity, firefox.exe consumes 0% cpu and just waits something. After that it opens and work as before, no problem at all. I tried to investigate it and found some dependence on firewall settings. I use windows firewall (adding rules in advanced interface manually) and I have two rules for firefox.exe allowing all TCP and UDP outgoing traffic. When I delete these rules and create one which allows ANY traffic for all apps, firefox opens up instantly. Why that happens? What traffic firefox wants to send if it is not TCP or UDP, and why it hangs if firewall denies such unwanted traffic?

Krejt Përgjigjet (2)

more options

Open your firewall program. Make sure that it's set to tell you when an application tries to access the web. Then check out the list of programs the firewall knows about. Make sure that all programs you want to access the web are set to Allow, not Auto. Auto may not allow access.

more options

Unfortunately, Windows firewall doesn't have an option to notify about outgoing connections, it asks only if process tries to listen socket. Firewall is set up correctly, (any TCP and UDP allowed for firefox.exe) it doesn't block firefox, after it opens it works fine.