Chrome tabs intermittent hang or crash with white screen

Question

Environment:
* VM hosted on ESXi
* Windows Server 2012R2 (v6.3 build 9600) with patches current to Oct 2019
* Server is running remote desktop services
* Server is part of a Windows domain
* Domain is using Google provided group policy templates
* User count on the server is about 20
* Chrome version 78.0.3904.97 (stable)
* Antivirus in use: Trendmicro Serverprotect 
Problem description:
Our users, at seemingly random intervals, experience their tabs going completely white and becoming non responsive. The portion of the tab that fails is only the rendering portion of the rendering pane. When the issue occurs, the display pane for the tab goes completely white. This is the case even if the site in the tab has been completely loaded. The browser its self does stay active. While all functions are operational above the display pane, the pane its self is completely unresponsive to input. As an example, with a tab experiencing the issue in focus, pressing F12 to access developer tools does nothing. With the same tab in focus, you can use the chrome browser menu to invoke the developer tools and they will be displayed as expected. Another example is right clicks or keyboard input into the failed pane is non responsive. Issuing input to the browser, such as reloading the pane or opening a new tab, gets the expected result. An immediate fix to the failed tabs can be to restart the browser, however, after a significant wait, they will regain functionality. Our timing puts the wait at somewhere around 15 minutes. Also, as a note, when using procmon to inspect the PIDs of the failed tabs, we can see the constant creation and termination of threads. Those threads however, seem to do nothing. 
Attempted Solutions:
* disabling hardware acceleration: no change
* disabling 3d graphics apis: no change 
* disabling antivirus: no change
* running chrome with administrative privilege: no change
* clearing chrome cache: no change
* server reboot: no change
* firewall reboot: no change
Notes:
I'd say its safe to say we are running out of ideas here. As a last resort we may try a re-install of Chrome, but I am wary of causing our users to lose settings, bookmarks, passwords and such. At this point I'm even wondering if a downgrade is possible. If anyone has any insight, we could use some help.
Thanks,
D.
Edit: 11/14/2019
Thanks to the input from many sysadmins we have more info and possible workarounds. I'll list them below. 
* Most effective workaround thus far: Turn off Occlusion in chrome://flags. Unfortunately this can not be set via GPO.
* Replicating the problem: We can successfully recreate the issue by having two users on the same RDS server running chrome with multiple tabs. User 1 issues a force lock of their session via Win+L. User 2 then experiences their tabs becoming hung / locked. 
* When a user experiences the problem, minimizing chrome and then bringing it back into focus will make the website content visible again, however, in our experience, tab functionality is not restored. 
* Command line arguments: some arguments disabling chrome features have been discussed. We have not tried any of those yet.
* For admins with larger networks it has been reported that this command line argument may help as opposed to setting the Occlusion off in flags. --disable-backgrounding-occluded-windows. We have not tested this though.
Hope this helps out our fellow admins. Good luck.
D
Edit: 11/14/2019
* Link to the bug report on the chromium project: https://bugs.chromium.org/p/chromium/issues/detail?id=1024837

Chrome Enterprise · Accepted Answer

Our mission is for Chrome Browser to be fast and efficient. We’ve been working on an optimization for when Chrome is hidden behind another window, to avoid having to draw content that a user will never see.
 
This optimization was tested in the Beta channel of Chrome for the past 5 months, and was activated for all users of Chrome 78, on Nov 12.
 
After the roll out, we received reports that in some virtual environments, Chrome on Windows displays a blank page, which may be because Chrome mistakenly believes it's covered by another window. As soon as we confirmed the reports, the feature was disabled.
 
If Chrome on Windows is displaying blank pages, restart Chrome. On the next start, this feature will be disabled.
 
We also want to provide an explanation of how this change was rolled out. For some features, Chrome uses a gradual roll out process that happens more slowly than the main roll out. This allows us to quickly revert a change if we discover a bug that wasn't uncovered in prior testing.
 
Once we received reports of the problem, we were able to revert it immediately.  We sincerely apologize for the disruption this cause