Closed
Bug 538349
Opened 15 years ago
Closed 14 years ago
Simultenious opening & closing the application along with maximizing and minimizing it sometimes throwing an error message and application can not be opened until the system is restarted
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: rudraneel.tester, Unassigned)
Details
(Whiteboard: [closeme 2010-10-25])
Attachments
(1 file)
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6.3; InfoPath.2; .NET CLR 1.1.4322)
Build Identifier: Firefox/3.6b5
Simultenious opening & closing the browser along with maximizing and minimizing it sometimes throwing an error message and application can not be opened until the system is restarted
Reproducible: Sometimes
Steps to Reproduce:
1.Open the browser, maximize it or minimize,again close then again open the browser and repeat the same process for 5 to 6 times
Actual Results:
After closing browser properly when user is trying to open the browser again it is showing error message that is
"Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system". The browser can be opened until system is restarted.
Expected Results:
Application should not throw any error message
Reporter | ||
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
Extensions are the most common cause of this. You can disable them, try safe mode, or create a new profile, but they are the usual cause of firefox.exe hanging when it closes.
Comment 3•14 years ago
|
||
Rudraneel, did you find the problem to be caused by extension?
Whiteboard: [closeme 2010-10-25]
Comment 4•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•