But what about firefox, it has tabs

Cookie · 06-25-2008, 01:59 AM

What exactly is this memory leak you are all talking about? Please remember us non-tecky people who would love to get the windows jargons right.

phenom · 06-25-2008, 03:06 AM

I never really noticed too much of an issue with FF2, but I don't open and close many tabs anyway so maybe thats why.

As mentioned before the memory would be taken up with tabs open (the more tabs the more memory used) but when the tabs were closed the memory would still be tied up...with no real way to fix it. Not sure why its called a leak other than its the proper tech term for it. I always equated it with your brains falling out (morbid I know).

Flumpet · 06-25-2008, 10:21 PM

I like the comparison! Yeah, I'm not sure why it's called a leak, other than for the fact that slowly you lose available memory. Each time you opened a new tab it would require a little bit more memory. When you shut down that tab, you SHOULD get that memory freed up. But instead it wasn't, FF2 retained control of it somehow-it still had pointers to those memory segments.

So if you ran FF2 for a period of time, opening and closing tabs, eventually your machine would slow down and you would have to re-start FF2. I have had two tabs running in the past, without sound or graphics, that was taking a quarter of a gig of memory.

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

06-25-2008, 01:59 AM	#21 (permalink)
Cookie Status: Member Join Date: Jun 2008 Posts: 50 Credits: 37	What exactly is this memory leak you are all talking about? Please remember us non-tecky people who would love to get the windows jargons right.

06-25-2008, 03:06 AM	#22 (permalink)
phenom Status: Member Join Date: Jun 2008 Posts: 50 Credits: 39	I never really noticed too much of an issue with FF2, but I don't open and close many tabs anyway so maybe thats why. As mentioned before the memory would be taken up with tabs open (the more tabs the more memory used) but when the tabs were closed the memory would still be tied up...with no real way to fix it. Not sure why its called a leak other than its the proper tech term for it. I always equated it with your brains falling out (morbid I know).

06-25-2008, 10:21 PM	#23 (permalink)
Flumpet Status: Member Join Date: Jun 2008 Posts: 63 Credits: 39	I like the comparison! Yeah, I'm not sure why it's called a leak, other than for the fact that slowly you lose available memory. Each time you opened a new tab it would require a little bit more memory. When you shut down that tab, you SHOULD get that memory freed up. But instead it wasn't, FF2 retained control of it somehow-it still had pointers to those memory segments. So if you ran FF2 for a period of time, opening and closing tabs, eventually your machine would slow down and you would have to re-start FF2. I have had two tabs running in the past, without sound or graphics, that was taking a quarter of a gig of memory.