mojira.dev

Benjamin Carter

Assigned

No issues.

Reported

MC-56174 Minecraft drops to several seconds per frame as tick uses 100% cpu Duplicate MC-908 Game client crash in multiplayer (ClassCastException) Cannot Reproduce

Comments

I have deleted everything under both saves/ and stats/ directories. Does not seem to have helped.

Today was particularly uncooperative, took 27 tries to get the game to launch. Usually it's only in the single digits.

So I located the stats_unsent files under .minecraft/stats/, they have a modification date of August 2013. Removed them but the issue still occurs.

I still think this has to be some sort of race condition - there is nothing different the third (or sixth) time I launch the game that would make it start up when it failed all the times before that.

Also, I don't see the point of creating the file only to delete it.

I mostly play multiplayer. Loading up one of my single player worlds into 1.7.9, it added a stats folder, but I'm not sure how this helps. The problem occurs before the game even shows the Mojang splash.

I did not realize it was a duplicate when I opened it.

Log output from this event:

[18:07:01] [Client thread/WARN]: Something's taking too long! 'root.tick.gameMode' took aprox 12685.361454 ms
[18:07:01] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 12697.348802 ms
[18:07:01] [Client thread/WARN]: Something's taking too long! 'root' took aprox 12710.124873 ms
[18:07:10] [Client thread/WARN]: Something's taking too long! 'root.tick.gameMode' took aprox 8456.546508 ms
[18:07:10] [Client thread/WARN]: Something's taking too long! 'root.tick' took aprox 8470.243929 ms
[18:07:10] [Client thread/WARN]: Something's taking too long! 'root' took aprox 8478.603593 ms

This seems to be a duplicate of MC-36883.

I'm not sure how to use this workaround - my minecraft installation has no stats subdirectories under any of the directories under "saves".

I have been getting a similar issue. However, if I hit the play button again after the game crashes back to the launcher, eventually it will start up without crashing. I have provided the log from the launcher here with two failed attempts to start the game, with the profile set to use 1.7.4.