L3viathan
- l3viathan2142
- l3viathan2142
- Europe/Stockholm
- Yes
- No
MC-45019![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
A few seconds after loading up one of my creative worlds, the game crashes with the crash report attached below. From the two worlds I have tested (both creative test worlds), this only affects one of them. Both worlds are singleplayer worlds.
Haven't found this bug posted here yet, if it has been, please forgive me.
Players can only log in once, then lose connection and afterwards can't log in at all (io.netty.hander.timeout.ReadTimeoutException). A server restart returns to the state where they can log in again for a few seconds.
edit: Players are still shown as online in the server selection screen.
[16:20:31 INFO]: Job 'Version & Libraries' finished successfully (took 0:00:01.434)
[16:20:31 INFO]: Launching game
[16:20:31 INFO]: Unpacking natives to /Users/l3viathan/Library/Application Support/minecraft/versions/14w25a/14w25a-natives-1403101231555492000
[16:20:31 INFO]: Launching in /Users/l3viathan/Library/Application Support/minecraft
[16:20:31 FATAL]: Fatal error launching game. Report this to http://bugs.mojang.com please!
java.lang.NullPointerException
at net.minecraft.launcher.game.MinecraftGameRunner.getAssetObject(MinecraftGameRunner.java:232) ~[launcher.jar:?]
at net.minecraft.launcher.game.MinecraftGameRunner.launchGame(MinecraftGameRunner.java:146) ~[launcher.jar:?]
at com.mojang.launcher.game.runner.AbstractGameRunner.onDownloadJobFinished(AbstractGameRunner.java:177) [launcher.jar:?]
at com.mojang.launcher.updater.download.DownloadJob.popAndDownload(DownloadJob.java:122) [launcher.jar:?]
at com.mojang.launcher.updater.download.DownloadJob.access$000(DownloadJob.java:12) [launcher.jar:?]
at com.mojang.launcher.updater.download.DownloadJob$1.run(DownloadJob.java:86) [launcher.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [?:1.6.0_65]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [?:1.6.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [?:1.6.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [?:1.6.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [?:1.6.0_65]
at java.lang.Thread.run(Thread.java:695) [?:1.6.0_65][16:20:31 INFO]: Job 'Version & Libraries' finished successfully (took 0:00:01.434)
[16:20:31 INFO]: Launching game
[16:20:31 INFO]: Unpacking natives to /Users/l3viathan/Library/Application Support/minecraft/versions/14w25a/14w25a-natives-1403101231555492000
[16:20:31 INFO]: Launching in /Users/l3viathan/Library/Application Support/minecraft
[16:20:31 FATAL]: Fatal error launching game. Report this to http://bugs.mojang.com please!
java.lang.NullPointerException
at net.minecraft.launcher.game.MinecraftGameRunner.getAssetObject(MinecraftGameRunner.java:232) ~[launcher.jar:?]
at net.minecraft.launcher.game.MinecraftGameRunner.launchGame(MinecraftGameRunner.java:146) ~[launcher.jar:?]
at com.mojang.launcher.game.runner.AbstractGameRunner.onDownloadJobFinished(AbstractGameRunner.java:177) [launcher.jar:?]
at com.mojang.launcher.updater.download.DownloadJob.popAndDownload(DownloadJob.java:122) [launcher.jar:?]
at com.mojang.launcher.updater.download.DownloadJob.access$000(DownloadJob.java:12) [launcher.jar:?]
at com.mojang.launcher.updater.download.DownloadJob$1.run(DownloadJob.java:86) [launcher.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) [?:1.6.0_65]
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [?:1.6.0_65]
at java.util.concurrent.FutureTask.run(FutureTask.java:138) [?:1.6.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [?:1.6.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [?:1.6.0_65]
at java.lang.Thread.run(Thread.java:695) [?:1.6.0_65]
Since 14w26c, or possibly earlier, but after 14w21b, mob-minecart-behavious seems to have changed, making it impossible to eject mobs in some situations.
The problem seems to be that mobs (tested with zombies) immediately reenter the minecart when ejected, which can often not even been seen by clients, to them it looks like the ejection fails completely. On a server with higher tick lag it is clearly visible.
This doesn't always happen, it seems to depend on the setup and might be directional, but I'm not sure about that. It seems to have to do with mobs (and players) now ejecting minecarts in the activator rail block itself, rather than besides it as it used to be, as far as I remember.
If the ejection location is intended behaviou
s, I think mobs should maybe have a cooldown within which they can't reenter a minecart (a few ticks should suffice).To clarify, this worked in previous versions and broke in (probably) the latest snapshot.
Since 14w26c, or possibly earlier, but after 14w21b, mob-minecart-behavious seems to have changed, making it impossible to eject mobs in some situations.
The problem seems to be that mobs (tested with zombies) immediately reenter the minecart when ejected, which can often not even been seen by clients, to them it looks like the ejection fails completely. On a server with higher tick lag it is clearly visible.
This doesn't always happen, it seems to depend on the setup and might be directional, but I'm not sure about that. It seems to have to do with mobs (and players) now ejecting minecarts in the activator rail block itself, rather than besides it as it used to be, as far as I remember.
If the ejection location is intended behaviour, I think mobs should maybe have a cooldown within which they can't reenter a minecart (a few ticks should suffice).
To clarify, this worked in previous versions and broke in (probably) the latest snapshot.
Since 14w26c, or possibly earlier, but after 14w21b, mob-minecart-behavious seems to have changed, making it impossible to eject mobs in some situations.
The problem seems to be that mobs (tested with zombies) immediately reenter the minecart when ejected, which can often not even been seen by clients, to them it looks like the ejection fails completely. On a server with higher tick lag it is clearly visible.
This doesn't always happen, it seems to depend on the setup and might be directional, but I'm not sure about that. It seems to have to do with mobs (and players) now ejecting minecarts in the activator rail block itself, rather than besides it as it used to be, as far as I remember.
If the ejection location is intended behaviour, I think mobs should maybe have a cooldown within which they can't reenter a minecart (a few ticks should suffice).To clarify, this worked in previous versions and broke in (probably) the latest snapshot.
Since 14w26c, or possibly earlier, but after 14w21b, mob-minecart-behavious seems to have changed, making it impossible to eject mobs in some situations.
The problem seems to be that mobs (tested with zombies) immediately reenter the minecart when ejected, which can often not even been seen by clients, to them it looks like the ejection fails completely. On a server with higher tick lag it is clearly visible.
This doesn't always happen, it seems to be directional: The problem occurs when the railline is west-east and the only possible exit is south (when driving in either direction), and when driving north, while the exit is west.
To clarify, this worked in previous versions and broke in (probably) the latest snapshot.
Since 14w26c, or possibly earlier, but after 14w21b, mob-minecart-behavious seems to have changed, making it impossible to eject mobs in some situations.
The problem seems to be that mobs (tested with zombies) immediately reenter the minecart when ejected, which can often not even been seen by clients, to them it looks like the ejection fails completely. On a server with higher tick lag it is clearly visible.
This doesn't always happen, it seems to be directional: The problem occurs when the railline is west-east and the only possible exit is south (when driving in either direction), and when driving north, while the exit is west.
To clarify, this worked in previous versions and broke in (probably) the latest snapshot (14w26a).
Since 14w26c, or possibly earlier, but after 14w21b, mob-minecart-behavious seems to have changed, making it impossible to eject mobs in some situations.
The problem seems to be that mobs (tested with zombies) immediately reenter the minecart when ejected, which can often not even been seen by clients, to them it looks like the ejection fails completely. On a server with higher tick lag it is clearly visible.
This doesn't always happen, it seems to be directional: The problem occurs when the railline is west-east and the only possible exit is south (when driving in either direction)
, and when driving north, while the exit is west.To clarify, this worked in previous versions and broke in (probably) the latest snapshot (14w26a).
Since 14w26c, or possibly earlier, but after 14w21b, mob-minecart-behavious seems to have changed, making it impossible to eject mobs in some situations.
The problem seems to be that mobs (tested with zombies) immediately reenter the minecart when ejected, which can often not even been seen by clients, to them it looks like the ejection fails completely. On a server with higher tick lag it is clearly visible.
This doesn't always happen, it seems to be directional: The problem occurs when the railline is west-east and the only possible exit is south (when driving in either direction).
To clarify, this worked in previous versions and broke in (probably) the latest snapshot (14w26a).
Edit: Affects 1.8.1-pre4
I too run OS X 10.9, the same Java version (6, 64-bit) and play on the same server as the reporter, however this issue doesn't seem to affect me.
Hi,
we (as I said, I play on the same server) did some testing and the results are weird:
After disabling the hopper clock connected to our mob farm (flushing farm with tons of dispensers), the lag seemed to be gone. While this might lead to the farm being the issue here, that is strange for several reasons:
Hope this helps...
I think Toby Strange's issue is not related to this: Not all of our affected users have Nvidea graphic cards and they don't get the lag constantly.
We did some more testing: What might really be the cause (although this doesn't fully explain it) are the block updates happening at the time the clock sends a pulse. There are some thousand blocks updated (water) in a short time, which could cause the lag. However, this doesn't explain why it only happens to some of us and not at all (not even a noticable drop in frames) for the other people. Also, I'm certainly no expert at game internals, but as far as I understand it, that should cause server lag, not so much client lag (the server is doing fine).
Should we also do the F3 + C thing?
We noticed our freezes often occur at a specific position in the world (at a small tree farm north of spawn).
I never had this issue before, but yesterday, when I passed the tree farm, my game froze for about 10 seconds. The mob farm was turned off at that time.
If you have an Iron Foundry or something similar, then this might be a duplicate of
MC-44531/MC-44620Affects 14w03b.
Some observations:
On our (same one as the one Jemus42 reports for) server, the problem has occurred since 14w03b. However, since today it always happened when a certain player logged in. We managed to solve the problem (at least for now) by editing his playerfile and "teleporting him" from the End to the overworld. He was also in a minecart at the time when him logging in was apparently constantly causing crashes, and I have removed that in his playerfile, too. So this might have something to do with minecarts or The End (it didn't happen for players in the Nether and we have not dared to enter The End again).
This either doesn't happen in the Overworld, or only happens with large amounts of Endermen. When hitting and killing Endermen in the Overworld, no freezes occured.
How to reproduce:
1. Create new world
2. Enter Nether
3. Attach Item Frame to block
4. Put Item into Item Frame
5. Leave Nether
6. Reenter Nether
P.S.: This can also be used to dupe items: Place an item in the item frame and break the block it is attached to.
I made a short video demonstrating the bug (and the duping). Note the high entity count:
http://www.youtube.com/watch?v=U_8S18O-ic4
>try copying a minecart with pickblock+Ctrl with items inside.
it won't copy the NBT inside...
Minecarts aren't blocks, so it's expected that won't work. Although it might be cool to have the same feature for Minecarts and mobs with spawn eggs.
Happens if Enderman dies, affects 14w11b.
Sorry about that, couldn't find it, it probably was created almost at the same time.
Confirmed on OS X 10.9 with <del>Oracle Java 1.7.55</del> Java 1.6.65.
Duplicate of
MC-57831Why couldn't I find that one? I looked through all open bugs that affect 14w28a..
Works as intended.
If you want to set the world spawn, use /setworldspawn.
Works as intended, while you can eat golden carrots, they are classified as potion ingredients.
It does, although the behaviour changed slightly. Issue updated accordingly.
Works as intended.
Affects 15w40a: http://bilder.ding.si/2qO496ZPwI.png
Can confirm.
Meanwhile, the server console spams this line 20ish times:
[11:01:57] Netty Epoll Server IO #2/ERROR: java.lang.ClassCastException: io.netty.buffer.UnpooledUnsafeDirectByteBuf cannot be cast to em