Hi asanidar thanks for going into all this detail. It might take us a moment but we’d like to dig into this. We might need to figure out what kind of debug output we might want to put in to help track this down. No hypothesis yet from the team on what could be causing this so still working to figure out how to proceed.
Sounds pretty infrequent, but one thing is wondering if it has anything to do with monitor sleeping etc, resolution changes etc. (Our guess is likely not, but, to ask.)
We look forward to figuring this out and sorry for the hassle in the meantime. One thing that might be good to flip on now is advanced debug logging, which you can find in About → Troubleshooting → Enable advanced logging? (Log out and back in or reboot to enable once you turn on, and it gives a chance for information to be logged, so that you can submit a report via Troubleshooting → Create Error Package after the next occurrence. There is likely already enough information in the logging to get an idea, with this advanced logging enabled and alongside the screenshot you shared.)
Thank you!