Can confirm for 26.12. Wasn’t this bug fixed for an earlier version or am I misremembering things?
Can confirm for 1.21.120 on Windows 10. This is the 1st time I’ve seen this error happen to me and it just started right after I updated to this version.
Can confirm for 26.12. Wasn’t this bug fixed for an earlier version or am I misremembering things?