Anatomy of a hang

[Beestie]

I don't know much about hardware or software but I have some guesses:

1. Firefox has a memory leak; and/or
2. Firefox inadvertently creates multiple references to the same memory address; and/or
3. Firefox creates partially overlapping references to the same memory block ; and/or
4. Firefox has some unmapped cases in its algorithms.

I've installed and uninstalled Firefox quite a number of times on several computers and have decided that while I like the program a lot, it needs a few more minutes in the oven.

Clarification on point #1. I don't necessarily think its a true memory leak because the task list does not reflect excessive memory allocation to Firefox. But the way it starts behaving makes me wonder if somehow, Firefox thinks all the memory is tied up and therefore unavailable leading it to freeze which somehow cascades into a general PC lockup. I dunno but I'm past tired of trying to get that program to act right.