mojira.dev
MC-44800

Lag on snapshot 14w02c

I can hardly play the new minecraft snapshot because of a major lag. It lags when I mine, open/close doors, monsters lag, sky movement lags, mine carts lag the worst, I don't know if there are any more things that lag but it's really annoying to play! Please fix it!

Linked issues

Attachments

Comments 17

Please attach the complete output of the "Development console" which can be found on the second tab of the launcher.

If the launcher closes after game start, please edit your profile and select "Launcher visibility" then, "Keep the launcher open".

I have added a log called 14w02cDevConsole.txt in which my sister and I experienced lag (sun jumping backwards, blocks popping back then finally breaking, etc.) trying to play multiplayer Minecraft via LAN. I have played with 14w02c on my 1.7.4-created world and had no problems with lag. I will create a new world in singleplayer and see if I can replicate this lag in singleplayer.

I have managed to semi-replicate the lag in SP, except it is just with FPS lag/freezes when in an environment with lots of trees, etc. When I went into an extreme hills biome, it stopped. Can provide a developer's console log if needed.

Might be related to MC-44531?

This is for a world seed: 9108691203762882539

I've ran around a bit and given the world time to load. Usually you have to break blocks 2 or 3 times before they stay broken, though its pretty random. For sure punching a tree right at the spawn in demonstrates severe lag.

GL fixing this. I look forward to new snapshots )

I think the relevant lines are:

[13:08:28 INFO]: Client> [13:08:28] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 20311ms behind, skipping 406 tick(s)
[13:09:27 INFO]: Client> [13:09:27] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4167ms behind, skipping 83 tick(s)

Not sure what it could be this is just a brand new world.

I've got a clean install of the latest 64 bit JRE. And up-to-date system. Also like to put out that I'm running win7 64bit on an AMD Athlon II X4 630 2.8Ghz (4 cores).

*update, re-created a new world with 14w03b (same seed), still has block lag, but its only about 3 seconds now and eventually the blocks break without having to break them multiple times. So vastly improved but still there.

7 more comments

Yeah, I understand your sentiment, just hoping things will iron out with the snapshots more myself. For reference I am using single player created worlds. No LAN play or server aside from the one built into the client.

My best guess is something got borked or a lot of behind the scenes debugging or disk OI issues. Or the server thread is being throttled somehow.

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

If I generate a new world with specific seed: 9108691203762882539 it lags for quite awhile, however on most worlds generated randomly it doesn't lag. The lag does resolve itself over time. Tested for about 5 minutes and still pretty laggy. Lag is still apparent at spawn in.

That's with 14w21b.

Here's a forced crash from 1421b during the lag at spawn. Chopping spruce blocks.

Works great, just tested it!!!!!!! Awesome! New engine updates in snapshot are pretty snappy 🙂

Dominick Hanson

(Unassigned)

Community Consensus

Minecraft 14w02c

Retrieved