Thread: Firefox 2.0 Due By Summer

http://www.pcmag.com/article2/0,1895,1914918,00.asp

Hopefully they'll fix the crash bugs before then.

As Adam would say, "true dat". Hopefully 2.0 will be so stable it will make Fred McMurray look like Ozzy Osbourne.

I'd also like to see Mozilla give me some of my RAM back on either machine, and also, stop stealing ALL of my processor cycles everytime I click a mouse button on a Mac.

Help stamp out processor cycle theft!

Originally Posted by Corey

As Adam would say, "true dat". Hopefully 2.0 will be so stable it will make Fred McMurray look like Ozzy Osbourne.

Hey, ol' Fred had a pretty decent jazz band Way Back When!

I know why FF crashes: not enough virtual memory (swamp file)...if you set it to 500 MB, it works perfect!

I know why FF crashes: not enough virtual memory (swamp file)...if you set it to 500 MB, it works perfect!

Agreed. That pesky swamp file will sink your canoe every time.

Heh.

Swamp file... That's such a good alternative name for it, actually.

The problem with excessively large swamp files is they cause disk trashing


Seriously though...

In systems that use virtual memory, the resulting condition of a hard drive being used excessively for virtual memory because the physical memory (i.e., RAM) is full. (The process of moving data into and out of virtual memory also is called swapping pages.) Disk thrashing considerably slows down the performance of a system because data has to be transferred back and forth from the hard drive to the physical memory.
A sure sign that your computer is thrashing is when an application stops responding but the disk drive light keeps blinking on and off. Thrashing is generally caused by too many processes competing for scarce memory resources. To temporarily stop thrashing, you need to terminate one or more applications. To stop it permanently, you need to install more main memory.

Disk thrashing can result in permanent failure of the hard drive; as the data is transferred back and forth, the hard drive’s read/write heads are subjected to considerable wear and tear.

http://www.webopedia.com/TERM/D/disk_thrashing.html

well, max 1GB if fine...but not more than 5 GB or...ouch!

Originally Posted by playmenow

well, max 1GB if fine...but not more than 5 GB or...ouch!

It is usually a good idea to include a source for any numbers you throw out...especially when commenting on values that could cause poor disk performance or failure...

Simply throwing out random numbers without significant data to back them up can cause people to disregard any valid info you might try to disseminate in the future.

As far a FF goes I don't really have any problems with the current version and I won't be upgrading (beyond test purposes) until all of my favorite extensions support the new version.

It's an interesting phenomenon how many people share your position on not updating FF until their favorite extensions are ready for each version.