I was wondering why my Firefox was taking up a lot of my system resources recently, processor rather than memory.
I noticed that when I had the Goat open my processor percentage used by firefox was up to 50% (that's one full core), even when i was doing nothing and it would usually idle at 0 or 1. I wondered if it was a Firefox problem so i came onto the site using IE and noticed that IE was really using too many resources than it should be (about 30% processor when not even doing anything except viewing the forum page). It was only happening when i had the Goat tab open in FF or IE, not when I had another tab open.
So I had a think (it took time, let me tell you!) and I think I've worked it out. The damn snow script must be doing it. So I've blocked it and now my processor is back to normal and I'm not noticing things like my text freezing when typing a post and am a happy bunny again.
Anyway, it's probably just me, but I thought I'd mention it in case others had noticed it and wanted to fix it. I don't know how to specifically stop it in IE, but I can show people how to stop it in firefox if it's causing them the same problems.
/geek
I noticed that when I had the Goat open my processor percentage used by firefox was up to 50% (that's one full core), even when i was doing nothing and it would usually idle at 0 or 1. I wondered if it was a Firefox problem so i came onto the site using IE and noticed that IE was really using too many resources than it should be (about 30% processor when not even doing anything except viewing the forum page). It was only happening when i had the Goat tab open in FF or IE, not when I had another tab open.
So I had a think (it took time, let me tell you!) and I think I've worked it out. The damn snow script must be doing it. So I've blocked it and now my processor is back to normal and I'm not noticing things like my text freezing when typing a post and am a happy bunny again.
Anyway, it's probably just me, but I thought I'd mention it in case others had noticed it and wanted to fix it. I don't know how to specifically stop it in IE, but I can show people how to stop it in firefox if it's causing them the same problems.
/geek