FWIW some people are still reporting this issue, but at the moment it's infeasible for us to fix it as it appears to depend on specific and currently unknown hardware/driver combinations.
Since as far as I'm aware nobody has yet reported the issue to Google as I advised, I created a report myself with what little we already know about the problem here: https://bugs.chromium.org/p/chromium/issues/detail?id=1501367
Predictably the response was asking for details about affected devices.
If anyone can provide the information Google are asking for in that issue report, it may be possible for this to be fixed relatively quickly. If nobody does this though, this will only be fixed in several years after all the affected devices fall out of use.