[MC-6330] Sometimes the game speeds up randomly

Resolution

This report is invalid as this bug seems to be caused by Java.
See @unknown's comment:

That would be most likely a Java issue

At random times, the game will speed up by a lot and after a few seconds will return to normal.
Has not happened in a superflat world. There seems to be no "real" way to reproduce this, but it does happen and has happened before in the snapshot.

Play a world for long enough. You will get it eventually.

Attachments

crash-2013-01-06_23.57.01-client.txt

Comments 17

kumasasa 2013-01-06T10:20:12Z

Please force a crash by pressing F3 + C for 10 seconds while ingame and attach the crash report here.

FireHunterX 2013-01-07T04:58:24Z

Please bear in mind that it says "Is modded: Very likely, Jar signature invalidated".
...Because I replaced char.png with a copy of my skin so that it shows offline.
Also note that it says "Suspicious classes: No suspicious classes found."

FireHunterX 2013-01-07T22:08:49Z

Not to be confused with some computers that go to sleep causing this upon wake.

That is the game catching up.
This is when it just happens for no reason, as if you are in a lagspike and the game is catching up.

Alexander Hammett 2013-01-19T11:30:17Z

The game catches up when you put it to sleep over night?! I just had it happen to me. Never happened before...

kumasasa 2013-01-19T17:22:20Z

Start the game with

java -Xmx1g -Xms512M -cp Minecraft.exe net.minecraft.LauncherFrame

and look if the console reports something like

Cannot catch up, did the system time change ?

7 more comments

FireHunterX 2013-01-22T12:43:45Z

Right.
I assume the same result will occur if I use Minecraft.app instead of .exe?
I use a Mac.

FireHunterX 2013-02-01T14:02:51Z

I got:

Time ran backwards! Did the system time change?

About 5 minutes after the speeding up ended.

Tails 2013-03-17T19:33:46Z

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

FireHunterX 2013-03-27T11:57:59Z

This does not seem to happen anymore. I'm willing to say that it should be closed.

David Harmon 2013-08-13T01:50:10Z

No, this is current – it happened to me last month (ETA: 1.6.2), and it's been recently reported by another Wiki user at http://www.minecraftwiki.net/wiki/Talk:Day-night_cycle#Timelapse_bug.3F .

It was also encountered by the Ultra Hardcore crew: http://www.youtube.com/watch?v=trCSukJNLag . Skip to around 8:45, which is when they first see speedy monsters – it takes them a while to realize the sun is speeded up too. They fixed it with a server restart.

kumasasa 2013-08-13T04:59:29Z

From http://www.minecraftwiki.net/wiki/Talk:Day-night_cycle#Timelapse_bug.3F

Timelapse bug?
The other day I took the latest update, . It contained several bugs, which I'm not going to bore you with, but one, though, since it is of interest to this article. You see, I had played until my computer entered standby mode. Then, when I reopened it a few hours later, I looked to the sky, and the Sun moved with tremendious haste! And that wasn't it, the cows in my farm ran like they had inhaled kilograms of concentrated heroine. Then, I dived into the water, and drowned before I could blink! Cooking wood was speeded, everything. Except for myself. I was still the same, unhyped Player. Is this a bug?
That happens when you forget to pause the game. Minecraft5025 19:30, 22 August 2012 (UTC)
Same thing can also occur on servers while running. It has happened during the twelfth season of Minecraft Ultra Hardcore. See: http://www.youtube.com/watch?v=trCSukJNLag (Skip to around 8:45, this is where the players start finding out something is wrong.) A server reset later fixed the issue, but the occurrence seems random. --UltimateBacon 10:54, 31 July 2013 (UTC)
Heh – that happened to me once last month... fortunately I was at my farm, so I was just mystified rather than slaughtered. You can still see my confused comment over at Talk:Chicken. Also, this has been reported as MC-6330. --Mental Mouse 01:48, 13 August 2013 (UTC)

David Harmon 2013-08-13T10:30:03Z

@Kumasasa: Thanks for reopening the bug. Is it SOP for a Wiki report to copy the entire report from there? I thought I'd decently summarized it, but I can see why you might want a straight copy.

kumasasa 2013-08-13T16:50:26Z

I don't know what's SOP but simply copied all the stuff over here...

Talven81 2013-11-26T20:14:48Z

Is this still a concern in the current Minecraft version 1.7.2 / Launcher version 1.3.4 ? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Tails 2013-12-12T22:38:06Z

No answer, assuming no longer an issue.

marcono1234 2015-03-15T20:57:40Z

Confirmed for

1.8.3 massive tick speed up when leaving Mincraft (with open inventory) running and the pc goes into standby and then closing the inventory again

I am not sure if this relates to this, but I got:

[20:01:44] [Client thread/INFO]: [CHAT] [Feuerwerksrakete] * 1 an Marcono1234 gegeben
[20:11:56] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4215ms behind, skipping 84 tick(s)
AL lib: (EE) MMDevApiProc: WaitForSingleObjectEx error: 0x102
[21:51:06] [Server thread/INFO]: Saving and pausing game...
[21:51:06] [Server thread/INFO]: Saving chunks for level 'Neue Weltddd'/Overworld
[21:51:06] [Server thread/INFO]: Saving chunks for level 'Neue Weltddd'/Nether
[21:51:06] [Server thread/INFO]: Saving chunks for level 'Neue Weltddd'/The End
[21:51:06] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 205420ms behind, skipping 4108 tick(s)

(This can also be triggered when using a too high /gamerule randomTickSpeed and then setting it back to the default one)

Torabi 2015-05-30T11:57:05Z

When you wake your computer from standby, to Minecraft it appears that the time suddenly changed, and it thinks that it lagged and needs to catch up, so it runs as quickly as possible until it catches up to where it thinks it needs to be.