PasswordMaker Forums

Firefox/SeaMonkey/Mozilla/Netscape/Flock Browser Extension => Help and Support => Topic started by: Addison on April 02, 2006, 05:19:00 AM

Title: Serious problem with Google Safe Browsing
Post by: Addison on April 02, 2006, 05:19:00 AM
I didn't know if you guys had covered this, and I figured it wouldn't hurt to post it either way. But in the last couple days/weeks I had been experiencing ridiculous memory leakage and cpu usage due to firefox. I did a whole slew of things...virus scans, uninstalling firefox, ad-aware thinking it was some spyware bug...just lot's of stuff which did a lot of nothing. It was terribly crippling to my computer. Firefox would start out at 90k Kb or higher and increase in memory usage by 150 kb every second endlessly until my computer would freeze.

WELL, all it was was the Google Safe Browsing extension sucking ass (sorry, I don't know the technical reasons). After uninstalling that everything works pefectly again. I hope this might be useful to somebody out there.
Title: Serious problem with Google Safe Browsing
Post by: tanstaafl on April 03, 2006, 01:54:42 PM
Hi Addison,

Yeah, its definitely a pain in the butt sometimes. I have 49 extensions installed myself (sheesh... haven't counted in a while), so you definitely have to be careful when laying blame for issues like yours. I see a lot of posts from people crticising FFox for being buggy, when 9 times out of 10 it is a problem with their pfofile and/or extensions. I'm not saying FFox is perfect, but it certainly has been extremely stable for me, even when using Beta builds, etc.

Anyway, glad you were able to figure this out.
Title: Serious problem with Google Safe Browsing
Post by: Eric H. Jung on April 03, 2006, 03:25:17 PM
Quote
I see a lot of posts from people crticising FFox for being buggy, when 9 times out of 10 it is a problem with their pfofile and/or extensions
So it is with Windows. Many times it's a kernel-mode driver, written by a third-party (not MS) which blue screens Windows. People misinterpret this as Windows instability.