Jim Rees
Assigned
Reported
Comments
Why? If you haven't fixed it in three years, is there any realistic expectation that you will ever fix it?
Sorry, four years.
This is still broken in server 1.11.2, although the line numbers have changed:
at le.b(SourceFile:54) [minecraft_server.1.11.2.jar:?]
at le.a(SourceFile:44) [minecraft_server.1.11.2.jar:?]
Still broken in 1.8 despite what the status says. Also why is it "unconfirmed"?
I would like to patch 14w21b. I can make the patch if I can find the right class file, but it's not acy.class. How do I identity the file?
Still broken in 14w08a.
I was also unable to place boats in 14w06b. In 14w07a boats mostly work ok but there are still a few glitches. The worst is that often my boat will break when I get out of it, even if there is nothing else around and the boat isn't moving. Also squids can break a boat even if the boat isn't moving, but maybe it's supposed to work that way. The good news is that I think the de-sync issue is fixed.
I haven't seen this in a long time. Currently running 1.7.2. I suspect it is fixed.
I'm still seeing this in 1.7.2.
Another rather disturbing thing that I think is related is that if I get far enough out of sync, I can actually sail "off the edge of the world" into an unrendered chunk, and look back to see the edge of the world down to bedrock.
Also, sometimes when my boat is de-synced, it will "stick" as if it's dragging on the bottom, even though it looks like I'm in deep water.
My elaborate system of canals, some of them underground, is now just about useless.
This is still a problem with 1.7.2. How do you update the affected versions?
Still affects 1.5.
I just got something similar in 1.5. Brand new world, no RCON. There were two of us on, but the trace says just one, so this might have happened just after the other guy disconnected. No mods, no DDoS, nothing special at all.
---- Minecraft Crash Report ----
// You should try our sister game, Minceraft!
Time: 3/13/13 7:56 PM
Description: Exception ticking world
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
at java.util.HashMap$KeyIterator.next(HashMap.java:928)
at iy.b(SourceFile:196)
at iz.b(SourceFile:122)
at net.minecraft.server.MinecraftServer.r(SourceFile:454)
at hz.r(SourceFile:255)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
at java.util.HashMap$KeyIterator.next(HashMap.java:928)
at iy.b(SourceFile:196)
at iz.b(SourceFile:122)
-- Affected level --
Details:
Level name: world
All players: 1 total; [jc['LuckeyJim'/7448, l='world', x=-537.24, y=51.17, z=207.48]]
Chunk stats: ServerChunkCache: 972 Drop: 125
Level seed: 2106225363214519273
Level generator: ID 00 - default, ver 1. Features enabled: true
Level generator options:
Level spawn location: World: (-426,64,255), Chunk: (at 6,4,15 in -27,15; contains blocks -432,0,240 to -417,255,255), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Level time: 90082 game time, 90082 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 15721 (now: false), thunder time: 13873 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
at net.minecraft.server.MinecraftServer.r(SourceFile:454)
at hz.r(SourceFile:255)
at net.minecraft.server.MinecraftServer.q(SourceFile:397)
at net.minecraft.server.MinecraftServer.run(SourceFile:331)
at gp.run(SourceFile:573)
-- System Details --
Details:
Minecraft Version: 1.5
Operating System: Linux (i386) version 3.7.10-1-ARCH
Java Version: 1.7.0_15, Oracle Corporation
Java VM Version: OpenJDK Client VM (mixed mode), Oracle Corporation
Memory: 77103736 bytes (73 MB) / 185393152 bytes (176 MB) up to 778502144 bytes (742 MB)
JVM Flags: 2 total; -Xms128M -Xmx768M
AABB Pool Size: 5420 (303520 bytes; 0 MB) allocated, 4 (224 bytes; 0 MB) used
Suspicious classes: No suspicious classes found.
IntCache: cache: 0, tcache: 0, allocated: 3, tallocated: 63
Profiler Position: N/A (disabled)
Vec3 Pool Size: 14605 (817880 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Player Count: 1 / 8; [jc['LuckeyJim'/7448, l='world', x=-537.24, y=51.17, z=207.48]]
Is Modded: Unknown (can't tell)
Type: Dedicated Server (map_server.txt)This bug still exists in 1.4.7 server. I'm a bit surprised by this one. Aren't you guys Swedish? Don't you use non-ascii characters?
You have a bug in your server code. You run a public bug reporting service, so I reported it. I have provided all the information you need to find and fix the bug, should you choose to do so.
You closed the bug. It wasn't fixed. Someone (not me) re-opened it. I re-verified that the bug is still there. This took me about one minute. I did your testing for you because I'm a generous guy and want to help you out.
Did you thank me? No. You suggested that I have not done enough of your work for you, and that I should do more. I would like to remind you that you do not pay me for this work. In fact, I paid you for Minecraft.
Please do not close this bug. Other users will come across this problem. They won't know there is a bug, and will want to know how to get their server to run. They may search this bug database and find the solution. I know it took me a while to figure this out, although I don't remember exactly how long since it was over four years ago. If you close the bug, they may think it's been fixed, or they may not find the report at all.
Also, closing the bug report does not actually fix the bug. The bug is still there. You have obviously decided it's not a priority to fix this. But that doesn't mean it's fixed.