Google Chrome plays up

Darksky40 · 01 Jun 2015

I am having problem's with Google Chrome it keeps crashing. I click on to Google Chrome it opens up two windows at once together sometimes a third window opens up then a message comes up saying Google Chrome has stopped and then all the windows shuts down. There sometimes is another window or tab opening with Page(s) Unresponsive message. This problem goes on for an hour this is when I first switch on first thing and I get do what ever once things settle down. How do I stop this?

Windows Sniper · 01 Jun 2015

Darksky,

What webpages is your Chrome set to open when it starts up?

There are some issues at the moment with certain websites being opened in Chrome, especially Version 43 which seems to have disabled some services.

Can you also disable all plugins that are enabled to ensure there are no framework errors.

mitchell65 · 01 Jun 2015

I would get rid of Chrome which is too invasive for me and go with Firefox!
With a standard uninstall a lot of Chrome dross gets left behind. To completely uninstall Chrome use Revo Uninstaller!

Windows Sniper · 01 Jun 2015

mitchell65 said:

I would get rid of Chrome which is too invasive for me and go with Firefox!

That does not help solve his issue, there are many reasons for choosing Chrome over Firefox, and vice versa. It is personal preference.

mitchell65 · 01 Jun 2015

Windows Sniper said:

mitchell65 said:

I would get rid of Chrome which is too invasive for me and go with Firefox!

That does not help solve his issue, there are many reasons for choosing Chrome over Firefox, and vice versa. It is personal preference.

If you read my post again you will see that I was exprssing a personal view!

mitchell65 · 01 Jun 2015

OK will try to help cure the problem > First try running Chrome with all extensions/add ons disabled. Try this
How to disable add-ons/extensions in your browser?
Disable all add ons!

Darksky40 · 02 Jun 2015

Thank you for the Replies and messages and I have Google Chrome and Google Internet Explorer and I did try one thing someone mentioned was to delete or disabled the add-on's and that did work. But how do you delete or stop a Plugin as that message keeps appearing? I may try Firefox and can what I have saved on Bookmarks can there be problems? I seem to have sorted a problem by disabled an add-on.

Windows Sniper · 02 Jun 2015

Darksky40 said:

Thank you for the Replies and messages and I have Google Chrome and Google Internet Explorer and I did try one thing someone mentioned was to delete or disabled the add-on's and that did work. But how do you delete or stop a Plugin as that message keeps appearing? I may try Firefox and can what I have saved on Bookmarks can there be problems? I seem to have sorted a problem by disabled an add-on.

Because you have Disabled a plugin and it now works, this indicates that one of your active plugins is causing chrome to crash the page when loading.

I would suggest you manually turn each plugin on in turn, and when you find the problematic plugin you should report it to the Chrome App store.

For removing / blocking them completely, follow the third section as found here - https://support.google.com/chrome/an...42064?hl=en-GB

Glad the root cause has been identified however!

Darksky40 · 02 Jun 2015

Thank you for the reply and I will report it to Chrome any problem's and also will turn on Plugins but I did read that NPAPI Plugins don't work on Chrome Version 42 as I read there is a new on Chrome 45 and that maybe the reason why I was Plugin news flagged down. Thanks any way for the advice.

Windows Sniper · 03 Jun 2015

If you believe this to be the case, use this to turn NPAPI back on.

chrome://flags > Find "Enable NPAPI" and enable.

Be warned however, that as of Chrome V45, this flag will be removed and your plugins will need to be re-written to support the new hooks.

If this has resolved all your issues, could you mark the thread as resolved in the top right? It would help other users who potentially have the same issue as yourself by letting them know there is a potential fix in the thread.

Regards