456277 - High CPU and memory in Terminal Services Environment after going disconnected

Status: VERIFIED INCOMPLETE

(Firefox :: General, defect)

Description

[eric worthy]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1

I've set up a terminal server using XPUnlimited and 2X Terminal Server running under Windows XP SP3.  When users disconnect from the server instead of logging off, Firefox goes into a race state and consumes all available processor cycles on the processor it was running on and slowly eats up all available RAM.


Reproducible: Always

Steps to Reproduce:
1.Run Firefox and Minimize
2.Disconnect from Terminal Server
3.Watch all your machine resources slowly disappear in Task Manager.

Comment 1

[timeless]

http://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg

you have some choices.

here are possible steps:
1. log into your terminal session
2. start /belownormal firefox.exe
(or just run firefox and then decrease its priority w/ task manager/process explorer, or just run it normally and risk having to fight for cycles)
3. outside of the terminal session (probably as admin) debug>attach to process (following the instructions in the above url) to the firefox process
4. debug>go (to let it continue)
5. disconnect from your terminal session
6. debug>break
7. !analyze -v -hang
8. attach that file here

Comment 2

[Wayne Mery (:wsmwk)]

(In reply to comment #1)
> http://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg
> 
> you have some choices.
> 
> here are possible steps:
> 1. log into your terminal session
> 2. start /belownormal firefox.exe
> (or just run firefox and then decrease its priority w/ task manager/process
> explorer, or just run it normally and risk having to fight for cycles)
> 3. outside of the terminal session (probably as admin) debug>attach to process
> (following the instructions in the above url) to the firefox process
> 4. debug>go (to let it continue)
> 5. disconnect from your terminal session
> 6. debug>break
> 7. !analyze -v -hang
> 8. attach that file here

eric, can you supply the info requested in comment 1?
preferably with beta
 http://www.mozilla.com/en-US/firefox/all-beta.html

Comment 3

[Tyler Downer [He/Him]]

No reply, INCO. Please reopen if you still see this bug in Firefox 3.5 or later in Firefox safe mode (http://support.mozilla.com/en-US/kb/Safe+Mode) or a new Firefox profile (http://support.mozilla.com/en-US/kb/Profiles) with updated plugins.