not new at all, this has been known for a while. i guess the cause of it is still unknown otherwise this would have been fixed ages ago
not new at all, this has been known for a while. i guess the cause of it is still unknown otherwise this would have been fixed ages ago
It has been fixed now on v0.20.460k