I tried to close the game, and it's currently (I still haven't forced it to quit in the hopes I can debug what's going on) hogging my entire cpu doing exclusively a "do_wait" system call (according to proc). About half an hour ago, maybe ten minutes after I'd told the game to quit, the game process was in an uninterruptible sleep state, which apparently is usually a wait for io or similar. Now it's in a regular sleep state and taking one entire cpu. Data collection on this one is going to be tricky.
Steps to Reproduce
I don't know if I can reproduce this, but I'm keeping my client open in the hopes that we can collectively debug what's happening.
There are no comments to display.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now