
biOGE4N wrote:I have somewhat the same story! I was using Firefox at first but then moved to Chrome when it was first launched. It was fast, but was not stable! When after sometime i figured that it is best to stay with the old pal firefox! and moved to it! Then for a longtime it was only firefox until a couple of weeks before i moved to chrome so that if all the crash causing zombies are terminated then i could so stick with chrome!But day before yesterday my system started to keep on crashing! All because of GOOGLE chrome!
So i Again moved back to fiRefOX
But this time the others guys are not going to get me again!
Am gonna stick to firefox from now on!
GOOGLE CHROME IS FAST BUT NOT STABLE!
FIREFOX MAY NOT BE FAST, BUT IS STABLE!
And RELiABLE
So am gonna stick to stable theory from now on
![]()

edone automaton wrote:I started using waterfox a few weeks back, its a firefox variant but optimised to run on 64bit systems, which firefox isnt. I have seen some decent speed increases as well as faster startup. And up to now haven't had the 'using too much memory, restart' or whatever it is message that I used to get frequently with firefox. Another good thing is that it automatically imports all your firefox settings and addons etc. if you're running a 64bit system its well worth looking into.<br><br>This brings to mind an article I was reading somewhere a while back about the best firefox variants/ alternatives. I will dig it out and post it up, I think it was in some magazine I have.
mShred wrote:For the people having issues... Recently, the sessions with the HTS Forums have gone kinda wack. If you leave an HTS Forum page up for too long, and endless script will run and continue to eat up everyone's RAM. Make sure you're leaving the page after you're done. Post back here if that helps at all. But along with that, FF and Chrome are both great browsers. I use Firefox because I'm too loyal to let it go, despite everything annoying that has happened to it since FF 4. And Chrome is a damn good fast, lightweight browser. Don't be hatin ma peoplez.
limdis wrote:This. I was just confirming if this was the case. I was running into this problem and was about 80% sure it was due to the forums page being open.
anarchy420x wrote:I'm running a 64bit system 4gb ram with a wireless internet connection. Internet connection is one floor above me, so I get a moderate signal. I think add on's are cool, but I don't really use them because (from my gaming experience) add on's like to slow systems down. I'm pretty heavy on tabs when I am working or browsing; I probably average 6 open tabs, and peak around 15+. Typically, I leave HTS and FB open, which might be my resource issue. I figured it was FB constantly updating that was hitting so hard, but MShred brought up HTS forums. <br><br><br><br>I'm going to look into that, thanks.edone automaton wrote: ...waterfox...
centip3de wrote:I can't talk about Google Chrome per se, but I can talk about Chromium, the original 'Google Chrome'. In all honesty, I've never had a problem with it on either Windows or Linux and my computer is about 5 years old now with mid-range specs.
biOGE4N wrote:I have somewhat the same story! I was using Firefox at first but then moved to Chrome when it was first launched. It was fast, but was not stable! When after sometime i figured that it is best to stay with the old pal firefox! and moved to it! Then for a longtime it was only firefox until a couple of weeks before i moved to chrome so that if all the crash causing zombies are terminated then i could so stick with chrome!But day before yesterday my system started to keep on crashing! All because of GOOGLE chrome!
So i Again moved back to fiRefOX
But this time the others guys are not going to get me again!
Am gonna stick to firefox from now on!
GOOGLE CHROME IS FAST BUT NOT STABLE!
FIREFOX MAY NOT BE FAST, BUT IS STABLE!
And RELiABLE
So am gonna stick to stable theory from now on
![]()

acevic wrote:I do agree that HTS is awfully coded and hogs up RAM despite whatever browser you run it on.


mShred wrote:Whoa whoa, no one ever said that. I said that recently, a change has sparked that inconvenience. HTS DOES NOT hog up RAM. Leaving the script running does. Either way, that will be fixed momentarily. So I'd encourage people to post back here if their browsers have either continued or ceased to crash.

Users browsing this forum: No registered users and 0 guests