Closed Bug 1141627 Opened 9 years ago Closed 8 years ago

Firefox stops loading pages and I cannot kill the process

Categories

(Firefox :: Untriaged, defect)

37 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: flory, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.76 Safari/537.36

Steps to reproduce:

I run Firefox in safemode.  After some time it stops loading new pages.  All loads produce wait circles.  Then I exit.  Sysinternals Process Explorer shows the process still running.  Using CPU.  I try to kill the process and the CPU usage stops but the process will not exit.  


Actual results:

I cannot kill the process nor can I start another one.


Expected results:

The Firefox process should have exited.
The only solution is to reboot my computer.  Win7 64bit.
I am experiencing the same problem. I'm on Win7 32bit.
After any crash, when I try to start firefox I get:
Firefox is already running, but is not responding. The old Firefox process must be closed to open a new window.
When I select the end process option I get:
Your Firefox profile cannot be loaded. It may be missing or inaccessible

When I try to stop the process (or the process tree) from the Windows Task Manager, nothing happens.

My only solution is to reboot.
We are three having experienced this issue and reported it.
Here are the links to the two other threads : 
https://bugzilla.mozilla.org/show_bug.cgi?id=1142981
https://bugzilla.mozilla.org/show_bug.cgi?id=1143277
David, are you still experiencing this on the latest Firefox version? 
https://www.mozilla.org/en-US/firefox/new/

If yes, could you please try the suggestions made in Comment 4?
Closing this as incomplete due to lack of additional information from the reporter.

David, please feel free to reopen it if the issue is back and reproducible.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(flory)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.