Description of problem: Mozilla processes continue to run even after the Mozilla
window is closed. This means that the next time Mozilla is run Mozilla complains
that the "default" profile is already being used and that another profile needs
to be created to run Mozilla. Killing the Mozilla process manually resolves this
issue and the "default" profile can be used again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run Mozilla in "default" proile.
2.Close Mozilla window and log out of account.
3.Log back into account and start Mozilla.
Mozilla stated "default" profile was already being used.
The Mozilla process would die when the Mozilla window was closed or the
"default" account would be usable after a Mozilla window was closed and the user
account was closed.
This is a minor inconvenience for someone who knows that the Mozilla process is
still running and needs to be killed manually to access the "default" profile
again. However, inexperienced users were stuck and did not know what to do.
This bug seems to be very close to bug# 84596 is not a duplicate. The
description of Bug# 84596 is a little different, but the outcome is the same.
Oops, the previous comment should read This bug seems to be very close to Bug#
84596 if not a duplicate.
I have not noticed this problem lately, perhaps the bug has been fixed.
I haven't seen it in a while, but I'm pretty sure it's still a problem. Darin,
who does lots of the networking for the browser, says that it will be fixed as
part of the DNS rewrite that he's been working on.
It's actually a delay, not a true hang. Once the DNS request in question times
out, the browser will exit.
Does the problem still exist in the current version?
Closing due to inactivity. Please feel free to reopen this bug or refile this
bug against the latest release Fedora Core if you feel this bug is still