Closed
Bug 616509
Opened 14 years ago
Closed 14 years ago
The browser don't shot down
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: Caribooua, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b7) Gecko/20100101 Firefox/4.0b7 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b7) Gecko/20100101 Firefox/4.0b7 Same time the browser don't shout down, and I want restart again I have to go to in Windows Task Manager and close the program from there Reproducible: Sometimes Steps to Reproduce: 1.Shout down Firefox 2.Open Firefox 3.The system can open because Firefox is already open this is the message that I get
Please detail the results of the following shutdown methods: 1. File -> Exit 2. Clicking the X button Knowing if any plugins were running in open tabs at the time will also help.
Reporter | ||
Comment 2•14 years ago
|
||
No probably I don-t explain well the problem, Firefox is been close, the screen don't show the browser, because is been already close, but if you try to reopen, the system say that Firefox is again open, so I must to go to in the Windows Task Manager find Firefox and close the process. After this I can open again Firefox before same time no.
Comment 3•14 years ago
|
||
Mardag asked you which method you used to exit the browser. And if there was a plugin (Flash for instance) running in one of the tabs. Do you also experience it when you run in Safe Mode ? http://support.mozilla.com/en-US/kb/Safe%20Mode
Updated•14 years ago
|
Version: unspecified → Trunk
Comment 4•14 years ago
|
||
Reporter -> Are you still experiencing this issue? Have you tried safe mode?
Comment 5•14 years ago
|
||
Closing bug as Incomplete - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question
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
•