Hanging shutdown, 100% CPU usage

RESOLVED INCOMPLETE

Status

()

Firefox
General
--
critical
RESOLVED INCOMPLETE
10 years ago
9 years ago

People

(Reporter: Paul Glowiak, Unassigned)

Tracking

({hang})

3.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

When closing FF3, does not completely shutdown, and CPU goes to 100%.  I have to manually kill FF in the Task Manager.  Had the same problem with final FF2 version, too.  

Wondering if it something related to WinXp rather than FF?

Reproducible: Always

Steps to Reproduce:
1.  Close FF3 browser
2.
3.
Actual Results:  
Failed to exit cleanly and CPU sticks at 100%.

Expected Results:  
Cleanly exited.

Comment 1

10 years ago
With Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0 eMusic DLM/4.0_1.0.0.1, I've seen this hang a couple of times.  I didn't notice if CPU usage was pegged, but I did have to go and kill the browser process before I could launch FF again.
(Reporter)

Comment 2

10 years ago
(In reply to comment #1)
> With Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906
> Firefox/3.0 eMusic DLM/4.0_1.0.0.1, I've seen this hang a couple of times.  I
> didn't notice if CPU usage was pegged, but I did have to go and kill the
> browser process before I could launch FF again.
> 

It's shutting itself down as of this morning, but it's taking 15-20 seconds to do so.  This is after the window has closed, and I can tell since the system is dragging.  I'm running more than enough memory, and I have an Athlon 3800+ processor, so I was surprised, too.  

I did have a similar problem on an older machine during the beta, was running Ubuntu Hardy Heron, and I just assumed it was because it was in Beta.


Have you tried:

- Firefox's safe-mode to exclude extension/theme problems
- a new profile
- a reinstall in a new empty folder? 

http://kb.mozillazine.org/Safe_Mode_(Firefox)
http://kb.mozillazine.org/Profile_Folder

Comment 4

10 years ago
I found this happen again last night when I thought I was running in safe mode.  I was able to bring up the process in Process Explorer and look at the stacks of the threads.  The main thread was still active with traces like

SSSensor.dll!SsCreateScreenSaverSensor+0x12f
USER32.dll!MoveWindow+0x79
USER32.dll!GetWindowTextLengthW+0x9a
ntdll.dll!KiUserCallbackDispatcher+0x13
USER32.dll!PeekMessageW+0x167
xul.dll!gfxContext::GetCairo+0x2c54b
xul.dll!gfxPDFSurface::`vftable'+0x7d4
xul.dll!NS_CycleCollectorForget_P+0x1a5d0

SSSensor.dll!SsCreateScreenSaverSensor+0x12f
USER32.dll!MoveWindow+0x79
USER32.dll!GetWindowTextLengthW+0x9a
ntdll.dll!KiUserCallbackDispatcher+0x13
USER32.dll!PeekMessageW+0x167
xul.dll!gfxContext::GetCairo+0x2c54b
xul.dll!gfxPDFSurface::`vftable'+0x7d4
xul.dll!NS_CycleCollectorForget_P+0x1a5d0

USER32.dll!PeekMessageW+0x167
xul.dll!gfxContext::GetCairo+0x2c54b
xul.dll!gfxPDFSurface::`vftable'+0x7d4
xul.dll!NS_CycleCollectorForget_P+0x1a5d0

SSSensor.dll!SsCreateScreenSaverSensor+0x12f
USER32.dll!MoveWindow+0x79
USER32.dll!GetWindowTextLengthW+0x9a
ntdll.dll!KiUserCallbackDispatcher+0x13
USER32.dll!PeekMessageW+0x167
xul.dll!gfxContext::GetCairo+0x2c54b
xul.dll!gfxPDFSurface::`vftable'+0x7d4
xul.dll!NS_CycleCollectorForget_P+0x1a5d0

The other threads all seemed to be uncollected worker threads stopped in calls to kernel32.dll:WaitForSingleObject.

A couple had the stack

kernel32.dll!WaitForMultipleObjects+0x18
xul.dll!gfxRGBA::gfxRGBA+0x2032
xul.dll!gfxContext::GetCairo+0xe261

and four had the stack

kernel32.dll!WaitForSingleObject+0x12
nspr4.dll!PR_MD_WAIT_CV+0xc9
nspr4.dll!PR_GetPrimordialCPU+0x78
nspr4.dll!PR_WaitCondVar+0x3b
xul.dll!gfxWindowsPlatform::gfxWindowsPlatform+0xf9c

Sorry -- not a lot to go on, but it might point to issues with the garbage collection.

Comment 5

10 years ago
(In reply to comment #2)
> I did have a similar problem on an older machine during the beta, was running
> Ubuntu Hardy Heron, and I just assumed it was because it was in Beta.

GNU/Linux users, please try kill -ILL (or killall -ILL) to kill the hung firefox-bin if this happens again.
Not sure if there is an equivalent feature on Windows NT.

I have bug 425929 filed, and it still happens, but kind of rarely, so I cannot catch it.
Keywords: hang

Comment 6

10 years ago
I have the same problem with 100% CPU usage after exiting firefox 3.01.
The same problem is also mentioned here:
https://bugzilla.mozilla.org/show_bug.cgi?id=446265
https://bugzilla.mozilla.org/show_bug.cgi?id=447910

I used a new profile without extensions and safe mode, but the problem still occurs.

Comment 7

10 years ago
I guess I have the same problem.

When I exit firefox 3.0.3 the CPU usage goes to 100%, but I was able to isolate this behaviour to the situation when I have various tab opened and one of those in the "background" has a javascript running.

It's a javascript that issues an XmlHttpRequest which is kept pending by the server for 60 seconds (internal server, ajax application).

Sometimes firefox is correctly closed, but most of the times, looks when it's opened from longer time, it remains in the task list consuming 100% CPU.
I've tried without the javascript page and I never experienced the 100 CPU.

Since it's frequent situation for me, is there smtg I can do to help catch this bug?

Leo

Comment 8

9 years ago
do you see this with FF 3.5?
Whiteboard: closeme 2009-11-20
Version: unspecified → 3.0 Branch

Comment 9

9 years ago
please reopen if  you see with v3.5 or newer
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2009-11-20
You need to log in before you can comment on or make changes to this bug.