Overview Description: Mozilla hangs after you exit the app, after creating a new profile that is located in a directory other than the standard location for a profile (on windows XP (whistler). Steps to Reproduce: 0) create a directory 'c:\foobar' 1) start mozilla -profilemanager 2) create a new profile, but change the folder to be, e.g., 'c:\foobar' 3) continue to start the app, with that profile 4) when app has successfully started, do 'File->Exit' 5) look in Task Manager Actual Results: mozilla.exe (or netscp6.exe) is still "running" Expected Results: application should exit Reproducibility: 100% on Windows XP Beta 2 (Whistler), with both mozilla installer from 06/08 trunk, and with commercial build (with activation) 06/08 and 06/04 trunk Cannot reproduce on Win2k (Whistler's cousin) 06/09 Cannot reproduce with Linux comm. 06/07 or Mac comm. 06/07 trunk builds Additional Information: When you subsequently attempt to run mozilla again, a second process is created but appears to block on the other process (the DDE stuff). You can't run again until either the original process is terminated, or you reboot (thus killing the hung mozilla.exe)

John - Is this consistantly reproducible? Is this a edge case?

It was 100% reproducible at the time this was reported. However, with today's branch build, using the same steps, I cannot reproduce this bug. WFM.

worksforme too on build 2001090405