• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why does Firefox have to be so effing retarded?

StageLeft

No Lifer
Seriously, wtf. I have never in my 49 years of windows computing found an application that will not start if it was just closed without a stupid pause. I.e. if I close firefox and immediately start another session it says I cannot start until the previous one has finished closing. Sometimes this can take over 10 seconds. Why? This is absolute fail. Even the most buggy crap software doesn't do this. Also, firefox downloads updates as frequently as adobe acrobat, which is also terrible, so many times I will load it and have to wait while it installs some BS crap.

Thanks for listening!
 
What version are you running? Any particular plugins? I used to run into issues with Firefox when closing it and the process is still running in the background. Except mine never shuts down the process, I have to CTRL-ALT-DEL - Task MGr - End Process. Sucks. Since 3.* though I haven't had the problems.

Ever try turning off automatic updates? Same goes for your plugins, etc. You can turn off updates on those as well.
 
FF3. I MIGHT have a plug in to check on specifics of http posts but I am not sure and leaning toward no... I shoulid turn off the auto update🙂
 
http://support.mozilla.com/en-...+but+is+not+responding

Essentially, Firefox runs some processes on shutdown that continue running for a few seconds after the window actually disappears. These processes may take longer with various extensions installed. Once the shutdown process is complete, the lock on the profile is released and you can start a new session. It is frustrating; I wish I knew more about what FF was doing during that period. Perhaps this will be improved when 3.5 is released.

As for automatic updates, they aren't that bad. Compare IE security updates in the same period:

07/16/2008 3.0.1
09/23/2008 3.0.2
09/26/2008 3.0.3
11/12/2008 3.0.4
12/16/2008 3.0.5
02/03/2009 3.0.6
03/04/2009 3.0.7
03/27/2009 3.0.8
04/21/2009 3.0.9
04/27/2009 3.0.10
 
Yeah, usually takes a couple of seconds. But I'm always using some Beta version of FF (currently 3.5 Beta 4) so I always assume it's just beta software doing the beta thing.
 
Originally posted by: theprodigalrebel
Yeah, usually takes a couple of seconds. But I'm always using some Beta version of FF (currently 3.5 Beta 4) so I always assume it's just beta software doing the beta thing.

I'm currently running the same version. Have had no "delay" issues upon closing and opening (just tried and was instant). The only issue that I have with the beta version is that several of the plugins haven't been upgraded to work with it yet (but Adblock Plus works fine though! 😀 ). I've grown to love the speed at which FF loads pages vs IE.
 
The faster the machine the less time it takes to clean up on close. It's just a folder and settings cleanup on close.
 
I dont have this problem. Probably because I close open firefox in the morning and close it at night, but still...
 
Originally posted by: Engineer
The only issue that I have with the beta version is that several of the plugins haven't been upgraded to work with it yet (but Adblock Plus works fine though! 😀 ).

Set extensions.checkCompatibility to false.
 
Originally posted by: theAnimal
Originally posted by: Engineer
The only issue that I have with the beta version is that several of the plugins haven't been upgraded to work with it yet (but Adblock Plus works fine though! 😀 ).

Set extensions.checkCompatibility to false.

Thanks. Will try that (is that located in the settings or an .ini file?) when I get home!

😀

Edit: Thanks again. Found it on Yahoo and it's working...woooohooo! 😀
 
Seriously, wtf. I have never in my 49 years of windows computing found an application that will not start if it was just closed without a stupid pause. I.e. if I close firefox and immediately start another session it says I cannot start until the previous one has finished closing. Sometimes this can take over 10 seconds. Why? This is absolute fail. Even the most buggy crap software doesn't do this.

Actually it's a win. FF won't let you run 2 instances using the same profile to avoid corruption, this is a good thing. The fact that other apps don't have this kind of check is a bad thing. For a good number of them it probably doesn't matter too much, but for any that have as much on-disk state like the profiles in FF then it's absolutely should be doing a similar check. The real problem is just that it takes FF a few seconds to shutdown, that's what you should be looking.


the point is we shouldn't have to do this.

Right, because I'm sure it's just sitting there spinning not doing anything. Would you also tell someone to just pull the power to shut their computer off because it takes too long to shutdown properly?

the point is we shouldn't have to do this.

No, the point is that people are complaining about a feature that was put there by design without knowing why it's actually there. The FF devs wouldn't have added the check if there wasn't a chance of data corruption with concurrent profile access.

The FF source is open, if you want to know what it's doing on shutdown and see if you can make it faster then feel free.
 
49 years of windows computing?

if version 1.0 came out in 1985, it is 24 years old at the most. i don't think it was even a viable os until ver 3.0. I'm assuming the 49 is for rhetorical purposes or do you mean pc computing?
 
Originally posted by: gorobei
49 years of windows computing?

if version 1.0 came out in 1985, it is 24 years old at the most. i don't think it was even a viable os until ver 3.0. I'm assuming the 49 is for rhetorical purposes or do you mean pc computing?

Did you really have to think and calculate about that?
Well, since you've started, you might as well calculate how long he's been pc computing.
 
Firefox just won't start sometimes on my computer. The executable freezes, the window doesn't show up, and clicking again opens yet another "frozen" executable.
So I was forced to open the Task Manager, close all the firefox.exe and open it again.

That was fully updated and everything. And it was enough for me to install Chrome and uninstall Firefox.
 
Originally posted by: sswingle
I dont have this problem. Probably because I close open firefox in the morning and close it at night, but still...

Yes, same here. Keep FF open for most of the day and close it at night.
 
Originally posted by: Sam25
Originally posted by: sswingle
I dont have this problem. Probably because I close open firefox in the morning and close it at night, but still...

Yes, same here. Keep FF open for most of the day and close it at night.

I'll consider that alternative when FF has a "minimize to try" feature. 🙂
 
When I've had that issue it has always been a plugin or maybe a theme. I use these without problem:
Redshift V3
Adblock plus
NoScript
Shockwave Flash
looking at it now there are others installed but I'm not having problems.
 
This is what you do then it will almost always shutdown quickly. It is only when I leave it open for days at a time and the memory footprint has gotten quite large that it takes a while to shutdown. I'm not sure what it's doing(would love to know) but just notice the behavior.
 
sounds like ur pc is slow
and who closes and opens firefox in a fraction of a second over and over anyways. open it, use tabs, leave it open😛 i rarely close it. perhaps u are suing firefox like ie6..browsing without tabs or some such nonsense. in that case, don't blame firefox...get with the program
 
Originally posted by: MrChad
http://support.mozilla.com/en-...+but+is+not+responding

Essentially, Firefox runs some processes on shutdown that continue running for a few seconds after the window actually disappears. These processes may take longer with various extensions installed. Once the shutdown process is complete, the lock on the profile is released and you can start a new session. It is frustrating; I wish I knew more about what FF was doing during that period. Perhaps this will be improved when 3.5 is released.

Nope, it is just as bad on 3.5.

People should just drop FF to send a message and move to Chrome or IE instead since they provide sandboxing and are more secure than FF right now. FF is fast becoming the new IE of the browser wars and starting to really lag behind in important areas.

Edit: I had no clue it was a feature. Thanks for that info Nothingman. I just hope they have sandboxing in 4.0 so I can switch back.
 
Back
Top