Thanks for providing the update, @ileradeltercomondo.
That is the worst of my fears – that potentially, this issue is inherently a hardware architecture and implementation fault that cannot be resolved in software without massively crippling the function of the GPU. I hope this can be proven otherwise from Apple. Something perhaps to do with how Apple integrated AMD's GPU core into this particular generation of Macbook Pros? It has been a nagging hunch that I've had for a while, especially seeing how we haven't gotten any fixes or updates from Apple.
It has officially been more than a year since this was reported. I am still abhorred at how I was led to think this was Google's fault in my initial Apple tech support outreach.
Those who continue to parrot resetting NVRAM or to disable hardware acceleration, keep drinking the Kool-aid. The rest of us here are looking for a resolution to getting our machines working – the way they were spec'ed and advertised to us – and that we depend on the stability of our machines to work when we expect them to.
My display continues to glitch. The easiest way to reproduce this is to leave the MBP plugged into a second display, let it go to sleep for a few hours while you have a web browser window (or any WebGL application) running, and wake it up. That said, I have also encountered the same glitch without a second display. The trigger point is almost always waking the computer from sleep – although these days just coding a WebGL app and testing it on browser refreshes can also trigger it.
Have there been sufficient fellow users who have submitted a tech support case to Apple, quoting this discussion?
To the Moderator: what did you edit in ileradeltercomondo's post? Some transparency will be useful here given the nature of this case.