Omega Owners Forum

Chat Area => General Discussion Area => Topic started by: zirk on 22 September 2010, 10:55:21

Title: Google Chrome and OOF probs
Post by: zirk on 22 September 2010, 10:55:21
No pictures or avatars on OOF, happened yesterday, other Forums seem fine, IE works fine but runs slow on this lappy.

Tried freesh Chrome install still the same?, any thoughts?

Currently using a Netbook, Win 7, Atom 1.6ghz, 2Gb ram.

Chris.  :-/
Title: Re: Google Chrome and OOF probs
Post by: Jimbob on 22 September 2010, 10:59:50
fine on chrome here....just tried it out
Title: Re: Google Chrome and OOF probs
Post by: Jimbob on 22 September 2010, 11:02:19
as far as i can tell, theres not a lot of options in chrome to disable images, barring globally, with site excepted, not the other way round  :-/
Title: Re: Google Chrome and OOF probs
Post by: zirk on 22 September 2010, 11:03:51
Hmm, not sure then, it did do a heavy Win update yesterday, maybe thats knocked it out?
Title: Re: Google Chrome and OOF probs
Post by: zirk on 22 September 2010, 11:10:49
I did try a Chrome default reset, before doing a re install. Ive had this before sometimes on IE where just showed the small red box where the Pic should be, bit chromes showing nothing, also just checked around 6 other Forums there all fine, OOF related??
Title: Re: Google Chrome and OOF probs
Post by: cem_devecioglu on 22 September 2010, 12:41:42
most of of the pictures are loaded via photobucket or some other image hosting sites..

I have the same problem in job (not at home) as websense blocks photobucket..

however you may have another problem..

check your internet options and advanced tab..(show pictures etc)

also if you have a personal firewall this can block the image objects..

also you may try dropping the security level temporarily just to check..
Title: Re: Google Chrome and OOF probs
Post by: zirk on 22 September 2010, 18:34:46
Ok, did a malwarebytes check for funnies just in case still the same, did a ccleaner and some general cache, temp  and history tidy up, working fine now, it would appear google chrome has some sort of memory limitation before bits of it functionality start to fall of.
 ;)