I run into such a bug from time to time (Windows 10), but I have never caught it twice in a row. Usually, the next launch of Sigil starts the program without a problem.
I have an old computer and the "latest" drivers are 8 years old, so even if it's related to the graphics card or drivers, there's nothing I can do about it.
I remember
this change in the code, but I have the feeling that I see this message on average once every two months anyway.
I do not report it because:
- I usually work on my build, which may have other issues related to my changes, so I don't want to call the guards when only my private build is on fire,
- I can't repeat it until many weeks have passed and the error message reappears.
It is difficult to debug an error that does not want to be caught.