Firefox buggy?

Bri

As much as I love this browser, I'm interested to know if anyone has this problem (XP Home, 1.01 but happened in 1.0 also).

If I close FF, mostly if not always because my connection has dropped or it's crashed or some other annoyance, I have a problem restarting it. It asks me to select a profile, but I only have the one default one and I don't start with the -p extension EVER. It refuses to reload until I restart the computer (my choice, it doesn't recommend this) - it just sits there on the profile screen and tells me that current profile is currently in use (it's not!).

Any ideas? Out of laziness I keep working using IE and we all know that's not a good thing.

aidan_walsh

The fact that its asking for the profile usually means that the process is still running somewhere, you should take a look and see if you can kill it that way.

This isn't just a FF thing, I've experienced this with most versions of Mozilla browsers, though much less frequently with FF.

pickarooney

open taskman and kill all firefox-related processes

NotMe

Yeah I get this quite a lot where Firefox stops working and is using up a lot of RAM and I close it but it stays in the process list. I have to kill it manually.

Hobbes

I used to get that in Firefox 1.0 when I opened videos and then closed the browser while it was loading. Works fine in 1.01 now.

Also if you don't have adblock running, some adverts can spawn another firefox (through Flash) and that will sit in memory.

Bri

I run adblock and have upgraded to 1.01.

Do you mean ctrl-alt-del to kill it or something more? AFAIK it says it's closed fully in taksk manager, but I could be wrong. It's only intermitent but it bugs the sh it out of me.

Thanks.

Zombienosh

Firefox uses way too much memory on me, and its crashed a good few times

jor el

Haven't had many crashes with Firefox, but occasionally it does happen. I always found that after a crash, or killing it with ctrl-alt-del I can't start the app again. It shows up in the task list but not on the screen. I found a program in the Firefox install directory called xpicleanup.exe that I run after a crash/kill and Firefox runs away happily afterwords. I don't know what this is or why it works but it does. This applies to FF 0.9 up to 1.01 for me anyway. Try running that after a crash and see if it works.

Bri

Ok so. Thanks.

dawballz

Wll kinda thread stealing here but since you seem to be finished, and rather than start a new thread with basically the same topic(buggy firefox) I'll put it here...
Does anyone experience this:
When I'm downloading a large file.. anywhere from 100MB - 900MB.. If the download is going on a while(which it would be.. well 20 mins at least) sometimes the blue progress bar just stops moving.. Now this could be while I'm downloading at say 30KB/s and it will just stop all of a sudden.. It usually happens when Im near the end of the download..
What I have to do is download it in IE, and I have no such problem..
Seems like the server just stops uploading to me...

Hobbes

You can change to a different downloader app. At 900MB though I tend to use WSFTP rather then a browser.

Syth

When using Firefox on unix, firefox creates a file in the profile directory called lock. The existance of this file stops firefox from using this profile. If I ever have to kill firefox (killall firefox), I then have to remove that file. Does a similar profile protection measure exist in windows?