From time to time, with no warning, the game window will lose focus and minecraft will state that it is not responding. However, the map is still loaded, basically leaving the player immobile but still active as an entity on the server.
It occasionally occurs when switching focus to another window (the aforementioned unresponsiveness), but it is not consistent, and as mentioned before, it can happen whilst actively playing; the window loses focus, and becomes unresponsive. In neither case does the game pause, as if Esc was pressed to go to the menu. It also does not remember a previous key press, e.g. if the player is moving when the defocus occurs, they will stop moving.
This occurs in both single and multiplayer, and renders the game unplayable. The only solution to the defocus is to close the window, logging out of the server. This re-opens the launcher, stating that the game exited with an error code, yet does not write a crashlog to the .minecraft directory. The player is still an entity on the server; there is no logout message, and a non-LAN opened singleplayer world does not pause when the defocus occurs.
Closing the window to log out gives a disconnect.genericReason error in the server log (see attached). I have tested this using a local, singleplayer server, a multiplayer server hosted on the same computer, and also several multiplayer servers hosted externally.
After a period of time, which does not seem to be consistent (sometimes a few seconds, sometimes minutes), the game becomes responsive again, and can be used again.
I have not found any bugs which duplicate this on the bug reporter, On a slightly separate note I have found that I have a greatly reduced framerate in the affected versions of the game; I do not believe the two to be related, but it is a possibility. Also, the java.io.FileInputStream.readBytes error at the start of the server log has been occurring in all server versions since 1.6.1 on my computer, if they are launched with more RAM than is allocated by default, however this does not seem to have had any effect whatsoever on performance, responsiveness, etc.
I hope this report can be of use, thank you for your time.
Related issues
Attachments
Comments
migrated
kumasasa
This re-opens the launcher, stating that the game exited with an error code
No, closing the game by closing the window gives
Game ended with no troubles detected (exit code 0)
After having this issue:
Please attach the complete output of the "Development console" which can be found on the second tab of the launcher.
migrated
Here's the Dev. console output, from two separate attempts. Neither wrote a crashlog to the crash-reports folder.
Torabi
Well, something doesn't look right there, but it's hard to tell what exactly is going on. Let's have a manually triggered crash report: Hold F3 + C for 10 seconds while in-game, and attach the crash report ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt) here.
migrated
Here it is, whilst logged into my server, which currently has a lot of mobs loaded. If required, I can retry without these.
Torabi
My intuition is that the game is freezing during heavy garbage collection. First, I'd recommend removing all currently installed versions of Java (your crash report says it's using 7u25, you say you're using that and 7u51 in the environment field), and installing the latest version of Java (7u60).
Then, run the game, and enable the debugging screen by holding shift and pressing F3. This will display the profiler. Take a screenshot of the profiler with F2 and attach it to the ticket. See if the memory usage climbs or falls suddenly, particularly when the game becomes unresponsive.
migrated
Screenshot of a common position in my world, with debugging screen open.
Memory usage seems quite stable, although it starts at about 20% used on startup, then climbs to about 45-50%, and instantly falls back down to 20%, repeating cyclically, although I'm not sure of its default behaviour.
I've noticed that I cannot allocate more than 1GB of RAM for either the server or client, though I believe this is due to my reinstallation of java, so I'll try and find a workaround for this.
So far I haven't experienced any defocusing, , and so I think that it's fixed.
Thank you for your help!
kumasasa
The default answer for exit code -805306369 is this
This is a technical support issue, please follow the instructions of this guide: Exit Code: -805306369. If all that won't help, please use the Mojang Support Center.
The primary solution to this issue is to increase the memory for the JVM, but you have already -Xmx4G -Xms2G in your options.
migrated
The problem has returned with the latest update to Java (8u25); I originally thought it was due to the fact that I lowered the amount of RAM allocated, but reverting the value of -Xmx to 4G only seems to delay the freezes for a longer period of time after logging on.