MacOS – MBP Retina 2015: Graphical glitches after update to 10.12.4
google-chromemacosspotify
my Macbook Pro has random graphical glitches. Most of the time they are present in Spotify, and less often in Chrome. An example of such glitches is on the photo attached.
Is there a known solution to this problem?
Best Answer
You're not alone (see this thread: https://discussions.apple.com/thread/7908354?start=0&tstart=0). I had the same artifacts and reverting to 10.12.3 "solved" everything. Let's hope this bug will be fixed with the release of MacOS 10.12.5 (sadly, I doubt it).
This bug is known to the Chrome developers and has been filed under...
Issue 90461: Dictionary keyboard shortcut doesn't work in Lion
Basically the problems are timing issues for some websites which take too long to respond to information needed to show the dictionary.
This is what @resek@chromium.org says:
There's likely not much that we can do here. We have to block the UI
thread to implement this feature, which is bad and so that's done on a
timeout. If the web page takes too long to respond for the information
we need to display the popup, we give up and unblock the UI. If we
didn't do this, Chrome would look like it's hung, waiting on the web
page to respond.
We collect timing information about this, and most pages succeed well
below the timeout, but there's also some class of pages that do not
respond in time (more than 1500ms, which is what starts to be
perceived as sluggish/hung).
I would definately diagnose with Apple's hardware test but you can also look through the system log.
You should be able to see if a particular application/service is causing this issue.
System logs are in /var/log/system.log
Take special note of the TIME when an application crashes and then go into the log and see if there is something related to the keyboard/trackpad; or any particular patterns. You may find that after a crash a service is restarting and that service is consuming either
enough resources to put the keyboard/trackpad out for 10secs
there is an I/O conflict.
Worst case scenario you can (painstakingly) format.
I would be looking at why your computer is crashing in the first place and prevent such application(s) from crashing.
Best Answer
You're not alone (see this thread: https://discussions.apple.com/thread/7908354?start=0&tstart=0). I had the same artifacts and reverting to 10.12.3 "solved" everything. Let's hope this bug will be fixed with the release of MacOS 10.12.5 (sadly, I doubt it).