almost 3 years
ago -
SLG-Dennis
-
Direct link
Well, we actually each time tried to fix an instance of the issue, unfortunately another one popped up with different cause each time. So all I can say is that we're again working on identifying this one and will provide a fix once we did. Doesn't mean another instance with a different cause doesn't pop up later, unfortunately. Also not really a surprise, as we'vbe been rewriting all backend part for part to tackle the performance issues and it's not unlikely that similar issues pop up, as how loading chunks and syncing stuff works changes.