We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Spletno mesto bo delovalo z omejenimi zmožnostmi, medtem ko na njem izvajamo vzdrževalna dela za vas. Če članki ne rešijo vaše težave in želite zastaviti vprašanje, naša skupnost za podporo čaka na vas na @FirefoxSupport na Twitterju in na /r/firefox na Redditu.

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Firefox process won't die

mreynolds1978
mreynolds1978
more options

When I quit/close Firefox, wait 1 minute, then reopen Firefox, Firefox does not open...it just hangs.

When looking in my Task Manager, there are two firefox.exe processes running. Killing the process via the Task Manager is required to get Firefox to open/run again.

When I quit/close Firefox, wait 1 minute, then reopen Firefox, Firefox does not open...it just hangs. When looking in my Task Manager, there are two firefox.exe processes running. Killing the process via the Task Manager is required to get Firefox to open/run again.

Vsi odgovori (2)

silkphoenix
silkphoenix
more options

Please read this article to see if it helps:

http://support.mozilla.com/pt-BR/kb/Firefox+hangs#Hang_at_exit

mreynolds1978
mreynolds1978 Lastnik vprašanja
more options

I'm quite familiar with the issue you've proposed via this KB article. My issue, though, is quite different. I don't get the annoying "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.." alert box.

Further, with the known issue, the firefox process does eventually die. With this new issue, the firefox process never dies and appears orphaned.

Keep in mind this only started occurring after I upgraded to version 3.6.9 two days ago. There is no doubt in my mind something is broken in the newest build.

As a developer, I like adhering an important and well-known principle in the software development world when I build and maintain stuff: if it ain't broke, don't fix it. Sometimes I wonder/question if Mozilla developers hold the same conviction, given numerous new issues that make it into every new build of Firefox.

This also brings up another subject: does anyone do QA anymore? I like to test my stuff before letting others use it. It's extremely important to make sure your stuff is solid, before letting others use it. Cross your T's and dot your I's, for heaven's sake!