|
Description
Sometimes, when I try to open firefox, I get this error
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.
I propose to change that, including a button - "Close firefox now" :
Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process. [Close firefox now]
Tags:
(none)
Attachments
No attachments.
Duplicates
Comments
|
kazagistar wrote on the 22 May 08 at 19:42
|
Yeah... ps + kill or killall are not newbie friendly.
|
|
Eldmannen wrote on the 22 May 08 at 20:08
|
Yes, I have experienced this too.
I usually open a terminal and type "killall firefox" and then proceed with "killall children"
|
|
tbrminsanity wrote on the 22 May 08 at 21:41
| |
When that happens to me, I open up the system-resource-manager, find the firefox-bin process and kill it. But it would be nice if the system handled it.
|
|
x1sc0 wrote on the 22 May 08 at 22:20
| |
I have the same problem and this is a very good idea, above all, it will help the new users.
|
|
ofir_k wrote on the 22 May 08 at 22:35
| |
Sometimes it means that Firefox is closing and not yet finished doing all necessary steps, therefore it must be used with a great caution (it happens when, for example, I choose to close and save all open tabs when many tabs are open).
|
|
mp3phish wrote on the 23 May 08 at 03:01
|
@ ofir_k:
FF should display user feedback if it is doing real work in the background. But I agree with your general point. It must be used with caution.
I think the user should be warned that they are ending the task, and not actually just "closing" the program.
|
|
mb wrote on the 23 May 08 at 10:59
| |
The error that you've mentioned is from Firefox, not system. I don't think this could be fixed, at least not without cooperation with Mozilla.
|
|
wladston wrote on the 23 May 08 at 13:44
| |
mb, yeah, but the best category I could find for it was the "system" one. I'm hoping ubuntu devs are able to push this upstream!
|
|
peetie wrote on the 23 May 08 at 15:12
|
-1
The real solution is to fix firefox to not lock up if a plugin stops responding, or better yet have a lightweight watchdog thread which checks the sanity/responsiveness of all running threads.
There are two types of problems: 1. external dependencies (plugins etc)... these should never be allows to block the progress of the entire application; 2. Internal bugs (javascript, rendering, image libraries, OOM, etc)
sluggish can be understandable, but lockups are never ok.
|
|
sisto wrote on the 23 May 08 at 22:54
|
I disagree with peetie. Sometimes fixing bugs and developing new features introduce new bugs. Sometimes some bugs take a very long times to fix.
Fixing all bugs in Firefox so it never ever freezes is not possible. There are no perfect apps because humans develop apps and humans aren't perfect. They are only bug-free until you find the next bug.
Your ideas only work in the theory. In practice not so much.
|
|
DavidNielsen wrote on the 24 May 08 at 11:14
| |
-1, Firefox should be fixed so this kind of bug. It's absolutely not impossible to fix this.
|
|
peetie wrote on the 27 May 08 at 15:17
|
"Your ideas only work in the theory. In practice not so much."
Maybe not for you, but as a software developer with ~20 years of Unix/Linux systems programming I'm not making this up. If OS systems engineers designed software without robust scheduling & resource management we would all be using MacOS-5 and Windows-3.1.
|
|
Auzy wrote on the 27 May 08 at 15:52
|
Actually, peetie I feel is right in this case sisto, its a threading issue, and watchdog issue.
To give you a better idea of how it works:
Picture a road. Lets say you have 1 lane. If a car stops, every car stops, no progress is made until the front car moves again. In this case, you have 1 thread.
Now lets say u have one road, but you have imported vehicles from china coming in, if they fall apart, all the traffic stops. A lot of users will blame local drivers on the problem, but, the reality is, the imported car wasn't tested properly. In this case, you have 1 thread, and a faulty plugin. 1 dead car still wipes out all traffic.
Adding 1 more road may not help if drivers don't know how to change lanes.
Now ideally, every imported car has their own road. That way, if one fails, there's only certain points where the rest of them get stuck. Thats multiple threads. It makes life much easier, because you don't get penalised as often for other peoples mistakes. Multi-core systems also love this.
A watchdog is where someone watches the roads, so if there is a crash, people don't just sit waiting. The watch guard helps push the car out of the way, and put the driver in an equivilent car that works, or a blank one, that will get them to their destination, albeit, not always in the right way. Thats a watchdog. The ability to detect crashes, and act better on them.
So his right, what we really need to do is separate things into threads, and when one thread starts doing dodgy stuff, repair it, and if you cant, ignore it, or replace it with a blank.
In fact, its what high availability computing is about. Detection of faults, identifying faults, repairing/bypassing faults.
So I agree that peetie has the BEST solution to the problem. However, for now, I don't disagree with this idea, so +1. But I do believe peeties idea could help these problems occurring in most cases
|
|
bgfeldm wrote on the 29 May 08 at 15:32
|
from commandline:
pkill firefox
|
|
melkore wrote on the 3 Jun 08 at 14:07
|
This isn't a linux or ubuntu only issue. This happens in Windows as well. Open the system monitor and kill the process, just like in Windows.
-1
|
|
Auzy wrote on the 3 Jun 08 at 14:13
| |
Welcome to the 1990's bgfeld and melkore... Users of the 2000's expect that the fix for their program is implicit (ie, they know what to do automatically, it is implied). Killing an app is guesswork, because users don't have enough clues.
|
|
_sebastian_ wrote on the 9 Jun 08 at 21:49
|
I have this message on 3 occasions.
1) when I run Firefox with one of my two profiles and click a link in Thunderbird.
2) when flash hangs, I've got the feeling that flash has become worse since I upgraded to Hardy.
3) When Firefox (profile 1) is already running and I want to start it again
In case 1 and 3 the solution is simple, find the desktop with the open session and use it :-))
For case 2 ... kill firefox, har har
|
Post your comment
|
