I am running Firefox (always the latest non-beta) in Windows 7 Professional 32-bit. I ALWAYS run with add-ons disabled. After a while (depending upon my usage of FF), b… (funda kabanzi)
I am running Firefox (always the latest non-beta) in Windows 7 Professional 32-bit. I ALWAYS run with add-ons disabled. After a while (depending upon my usage of FF), but usually every day or every other day, FF becomes "non-responding". I have no idea what that term means in MS WIndows terms. When this happens, FF begins using up to 50% of the CPU, and is using 1.4 Gb of private space. When this happens sometimes the software will allow me to click "Exit" to terminate FF. Other times Windows will not allow me to click "Exit, andI have to use the Task Manager to cancel the firefox,.exe process. And, more times that not, when I am able to click Exit, Firefox takes a few minutes terminating before it crashes and gives me the option to cancel FF or restart it. I always send the dump to Mozilla. I have not looked at the recent crash reports.
This happened this morning about 15 minutes ago, and FF is behaving properly now. But it is already using 1.1 Gb of private space. i do not know if this private space usage is related to the problem. I do have11 FF windows in my current setup, as I use a different window for each project on which I am working. But so far I have only accessed two of the windows since the restart. I assume, that based on my projected usage of FF today, by tomorrow morning FF will have crashed by itself or I will have to Exit and restart.
What is happening? In MS terms, what is happening when a process becomes "non-responsive"? Is there some resource shortage that causes this? And when this happens, how can I debug FF and get more diagnostics? My records show that this has been occurring for over a year. Thanks.