Is this just me? I know it isn’t avast related, the Google Chrome browser became rather slow lately in rendering some pages for me in the browser - delivering errors and time outs while trying to get a response on a request.
I am not the only one (browsing on an acer Vista laptop)…
Read here: http://www.theregister.co.uk/2014/11/28/google_chrome_on_windows_completely_unusable_complain_users/
Yes, I see instability with the avast google chrome extension which was bad for some weeks and I had to click a balloon to reset it to work after it had crashed and the extension had greyed out. The extension performance is more stable now after a Google Chrome update to version 39.0.2171.71 m
What have the Google Chrome coders been changing around under the hood? I have noticed that it takes quite some while before a video starts playing from youtube.
Are these all coding incompatibilities with the browser now separately functioning “floating” on top of Windows -Google Chrome NativeClient implementation incompatibilities and this comes as Google “does not do anymore Windows (coding)”?
Anyone with similar buggy performance experiences?
Intrusiveness is not my main objection as this can be blocked or circumvented.
Script-blocking and ad-blocking and sand-boxing helps a lot towards that end.
What I loathe is that Google Chrome development now more and more restrict user preferences.
Only Google Web Store extensions allowed -
you need a special extension to run user scripts like malware script detection extension,
which was installed outside of the Google Web Store and therefore terminated by the “Google Overlords”.
And on their own android platforms they do not allow even ABP to run anymore
or you have to loop through various hoops and run it via a specific port.
Obvious there that it is meant to be an ad-driven and generating browser tool,
as that is their main line of income, “owning and selling your clicks”.
They do this restricting to a point where the average not so savvy user gives up.
And there where they have a monopoly position they are even more restrictive (Google OS).
The sad thing is that other software is copying these attitudes and trends more and more.
It is more and more popular now to restrict user choice
and we will get slowly to a “one fits all” uni-model, a “like this browser or leave it”.
@ NoelC,
Your personal opinion about Google, Chrome, etc aren’t really part of the question and therefore totally irrelevant. :o
[font=Verdana]@ Damien,[/font]
I’ve also on several occasions had a problem with Chrome’s speed and ability to display certain websites.
Quite often, it also becomes unresponsive.
At those times I’m glad I have a few other browsers at my disposal.
(Part of the problem can also be my own fault due to all the nice extensions I enjoy using…)
What also could be revealing is to click the Shift + Esc buttons at the same time to land at Google Chrome task management and you can see what is so consuming… What is also important to consider is the Google/Browser differences, as we have a statement from the Google delopers that “they won’t be doing MS code anymore”, and that certainly may affect Google Chrome running on Windows. Also they ended support for some api code etc.
I must admit as I run my personal flaw of Google Chrome browser inside sandboxie, I lately experienced less problems, except some site rendering hick-ups. Users that use Script safe and feel they are on a secure known site could temporarlily or for the session consider to set it to allow all. But you should be careful where to allow this.
And while bob3160 draw me to make the switchover to the Google Browser I must admit I no longer feel that urge toreturn to firefox, I am quite happy as how I tweaked Google Chrome browser and extensions to my liking.
Here you can read that security research is not particularly appreciated by Google developers. They probably strongly believe in security through obscurity and do not have need for busybodies as they terminated the security researchers accounts when they wanted to check a Java VM sandbox circumvention exploit.
Read: http://seclists.org/fulldisclosure/2014/Dec/26
Google did not react on the sandbox bypasses disclosure.
So there are certainly things going on with the Google browser code that we are not fully aware of.
