Strange Problem With Firefox on my Mac
#1
Original Poster
FlyerTalk Evangelist




Join Date: Oct 2002
Location: Currently in Bloomington, IN, but Normally NYC, CDG, and even POZ or wherever FT takes me.
Programs: Northwest Airlines. MTA pay-per-ride Metrocard; zero-balance Oyster card.
Posts: 14,082
Strange Problem With Firefox on my Mac
I'm having a problem with Firefox on my MacBook that I thought I would never see again, after having had the same problem for years with IE on Windows. 
Just recently, FF started "loading up" active and virtual memory, to the point that after 30-45 minutes of surfing, the whole machine slows down to a crawl, as 50-75% of active memory is dedicated to Firefox.
I remember this problem with IE, and it was "unsolvable" until Mister Softee finally released a usable version of Explorer. This was like 5 years ago, mind you. To have this problem on a Mac is shocking, just SHOCKING I tell you.
I'm 99% certain that the problem is with FF, not the OS. I have the latest version of FF, but only OS X 10.4 (though this should not matter).
Any ideas on how to solve this? Should I patiently wait until mozilla releases an u/g?
As it is right now, I have to restart my browser once an hour. For someone who works online, this is a major pain.
Any suggestions will be most appreciated. :-:

Just recently, FF started "loading up" active and virtual memory, to the point that after 30-45 minutes of surfing, the whole machine slows down to a crawl, as 50-75% of active memory is dedicated to Firefox.
I remember this problem with IE, and it was "unsolvable" until Mister Softee finally released a usable version of Explorer. This was like 5 years ago, mind you. To have this problem on a Mac is shocking, just SHOCKING I tell you.
I'm 99% certain that the problem is with FF, not the OS. I have the latest version of FF, but only OS X 10.4 (though this should not matter).
Any ideas on how to solve this? Should I patiently wait until mozilla releases an u/g?
As it is right now, I have to restart my browser once an hour. For someone who works online, this is a major pain.
Any suggestions will be most appreciated. :-:
#3
Original Poster
FlyerTalk Evangelist




Join Date: Oct 2002
Location: Currently in Bloomington, IN, but Normally NYC, CDG, and even POZ or wherever FT takes me.
Programs: Northwest Airlines. MTA pay-per-ride Metrocard; zero-balance Oyster card.
Posts: 14,082
Code:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 GTB5
The only plugins that I have are greasemonkey and flash.
Could it be a script running in conjunction with greasemonkey? It seems like that would cease once I navigate away from the page containing the script...
#7
Suspended
Join Date: Jan 2001
Location: ORD / DUB / LHR
Programs: UA 1K MM; BA Silver; Marriott Plat
Posts: 8,240
#8
Join Date: Jun 2002
Posts: 960
actually, very few. safari also gets 100% on the acid3 test, while firefox does not.
#10
Suspended
Join Date: Jan 2001
Location: ORD / DUB / LHR
Programs: UA 1K MM; BA Silver; Marriott Plat
Posts: 8,240
Most recent one I noticed (last week) was Barclays intl. online banking. Random buttons that are essential to its use are missing on Safari, fine on FF.
This was my most recent attempt at "trying" Safari - and with the same result. Delete. I've probably tried it on 20-30 separate occasions and found the same type of issues - the exact sites don't spring to mind. Even FF is only now at the point where the vast majority of sites work, but I have used it consistently for 3 years because it is light years ahead of any version of IE.
So Safari and Chrome stay in the bin for now. Just not compatible enough. Maybe some day. Acid3 tests just don't do it for me
This was my most recent attempt at "trying" Safari - and with the same result. Delete. I've probably tried it on 20-30 separate occasions and found the same type of issues - the exact sites don't spring to mind. Even FF is only now at the point where the vast majority of sites work, but I have used it consistently for 3 years because it is light years ahead of any version of IE.
So Safari and Chrome stay in the bin for now. Just not compatible enough. Maybe some day. Acid3 tests just don't do it for me






