The hamburger icon on the upper right, click on it then scroll down to help then click on About Google Chrome. This will force an update. Maybe this will help.

I was having a little trouble with Chrome being a little spastic a few days ago and I went in and disabled hardware acceleration again (I had disabled it on the previous version of WB, then gone back in and enabled it after the WB update).  That seems to have taken care of it for me (and honestly I can't see any difference between hardware acceleration enabled/disabled otherwise).  Might be worth a shot.

Chrome has been acting up of late. The throbber sometimes freezes, starts up again as the page is loading then freezes again. It doesn't happen here but when I go to yahoo sometimes the page will go black and mousing over clears part of it but I have to refresh the page to clear it all. I don't know if its a site issue or Chrome's new version is at fault. Same thing happened before I updated it.  

Quoting DrJBHL,

reply 6

gevansmd - 

It might be related (or not), but have you updated your Windowblinds to the latest version?

I had similar issues, and after updating, things were magically fixed.

I did but then restored the prior version.  The new WB beta breaks the built-in Windows 10 State Menu when you look at all programs.  Large letters of the alphabet are placed in two columns over the program names.  Support was unable to fix the problem but reinstalling the prior WB did.

I reinstalled the latest WB beta and the Start Menu problem has gone away.  However, still having the Chrome file dialog issue.  Unfortunately, rebooting doesn't fix that for me.

I had previously tried disabling hardware acceleration.  I even reset to default settings that unloads the extensions.  None of that worked.

However, I discovered now, if I unload WindowBlinds, the problem goes away.  

I tested the skin gevansmd, and apparently my Reddish skin, and the base skin I used to create it called Scarlet, both cause this issue. I have absolutely no idea why though and the only problem with those two skins is in Chrome. I will try and resolve this issue, but I have absolutely no idea where to even start. None of my other skins have the issue, just those two. I apologize for anyone having this issue and I hope to resolve it quickly. 

Maybe someone in support could have a look at either of those skins and see if they notice anything? It would be greatly appreciated. 

Well, I looked through everything and cannot see what is causing this issue, so I have asked for assistance from support. Ticket# KRC-836-86635.

The issue with Reddish has been found and the next WB update should address this.

I am waiting for a reply from support so I can fix Reddish and Scarlet Ross, as soon as I find out I will modify and upload the fixed WB's.

EDIT: Doesn't make sense to me, but evidently the problem may be with WB and not Reddish or Scarlet. It doesn't make sense because only those two skins have the issue, so how can it be WB itself? Also, the problem occurs it in WB 8.13 and WB10. Crazy.... 

I went through the .UIS file thoroughly Ross, I did not notice anything that might be causing the issue. Still waiting for information from Neil or support.

I would really like a reply to my PM to Neil or my last response to support on this 2 days ago.

I am assuming now that the issue was within WB10 itself and not the skin, but I am confused. How can it be just 2 skins that are causing the issue in Chrome, when all my skins are designed the same way?

Thank you.

EDIT: Heard back from support, the problem is not with my Reddiish skin:

WB will be modified to adapt to a Chrome issue. It will be in the next mini update.

Good to hear on my end!