Anatomy of a hang

Beestie · 03-21-2006, 01:24 PM

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.

dar512 · 03-21-2006, 01:28 PM

If you're not having problems in any other program, then I'd have to suspect Firefox also.

03-21-2006, 01:28 PM	#2
dar512 dar512 is now Pete Zicato Join Date: May 2003 Location: Chicago suburb Posts: 4,968	If you're not having problems in any other program, then I'd have to suspect Firefox also. __________________ "Against stupidity the gods themselves contend in vain." -- Friedrich Schiller

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

03-21-2006, 01:24 PM	#1
Beestie -◊\|≡·∙■·∙≡\|◊- Join Date: Feb 2003 Location: Parts unknown. Posts: 4,081	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. __________________ ♠ ♥ ♣ ♦ Last edited by Beestie; 03-21-2006 at 01:28 PM.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)