Wednesday, February 17, 2010

When Firefox stops responding

One problem that we all must have faced at some point of time in the CC or CSE Lab is the problem of firefox not responding. It gives the following message :



Even after restarting the system, it gives the same message.
Also, on typing "ps -e" on the terminal (which is supposed to show you a list of processes running), it doesn't show firefox.

I remember facing this situation during First year. I finally gave up and started using someone else's account.
Now I faced the same situation in CSE Lab, and decided to find out how to deal with it.
It's quite simple, really. Open the terminal and type firefox -profilemanager. It will open the firefox profile manager. Right now, the current profile is causing problems. So just make another profile. You will most probably lose all your saved passwords, etc.

Now open firefox and select your new profile on being asked to select a profile.

A better method which I read somewhere involved deleting a lock file in your profile folder. However, I could find no such lock file in my profile folder. If you do, let me know.

1 comment:

orangerinds said...

Haha. Nice find. Chrome has a better mechanism i guess. If you closed it down, and you reopen it while the process is in the decay chain, chrome simply initiates a quicker process end, and dies down quickly, much like Windows media player. Then you can click it again, and it will start jollily.

But nice find though. pure geek stuff! :D