Closed KeyboardInterrupt closed 4 years ago
This problem happens a lot to me during testing-- usually after a bunch of other CAOS-errors are thrown/autokilled because I am butchering everything. In my experience there doesn't seem to be a specific cause other than other 'things going horribly wrong'. Hopefully if we can correct those underlying issues, this will go away, but if we can narrow down anything specific, all the better.
@Amaikokonut Have you seen this one recently? I have not stumbled upon it that much recently. If there is no good way to reproduce this Issue, We should not prioritize it to much. When we find a reliable way to trigger this Bug, I will take a look at it again.
Yeah pretty much the only time I get this is when I am testing and something gets out of control from the CAOS side of things (brutal ignoring multiple caos errors for instance). I don't think this is a bug in and of itself as much as it is a symptom of problems with the CAOS. I haven't got this error in the course of normal gameplay in quite some time so I agree that it's not really worth priority right now.
This is made obsolete by the Switch to ReBabel
Sometimes the Client cannot open the Shared Memory Interface and crashes, we should try to find out what causes this...