Joseph Meyers
Comments
You guys do realize this error message occurs for hundreds of different reasons right? Did you even read through the entire defect? Mojang has fixed a multitude of bugs causing this error. A lot of us no longer experience this error due to the fixes Mojang has implemented. If you do not have anything useful to contribute do not bother posting. Tons of people posting complaints and not staying on topic clutters the defect and makes even less likely any new issues will get resolved.
Now that we have repeatable steps, hopefully someone at Mojang can work on this. My results were the same, lots of checkerboard water = crash. A reduced number of them it doesn't. Not sure if it's the water or the signs holding the streams up.
One cause of this error is discussed in this thread here with a possible fix for non-UNIX users.
You will see 4-5 maybe more tick skipping errors in the server logs back to back and then everyone will get kicked with the io.netty error. Sometimes it will even force the server to restart. This is one of the somewhat common cases with io.netty errors since 1.8
The problem is this error appears for multiple issues. Having too many mobs causes this and there was a bug fixed that was duplicating mobs en masse in one of the snapshots. The defect causing this error for me when I first joined this thread was also fixed (.dat file issue). Slow connections, java versions, and more also cause this and people in this thread have found solutions for whatever caused this error for them. As long as unrelated issues keep getting added to this thread due to having the same error message this will never be fully fixed. Don't think however that nothing will get fixed because we've already seen many causes for this error fixed in the past.
Some more information now that I've done more testing on when I get the error. I get this near a squid farm I build. It's basically a water source placed over a half slab that cascades down about 20 blocks. This is repeated to get a checkerboard pattern. At the bottom is a floor made of ~400 signs placed against each other. From what I can tell it may be caused by the flowing water or the signs. When it crashes it will continue to repeatedly crash for a while before finally going away. If I look down at the ground it seems to help but I haven't really been able to confirm that. It also goes away if I leave the farm area. Nothing shows in the server log other than my character disconnecting so it seems to be client based.
I am getting this all of a sudden as well. One second everything is fine, now I can't walk around the area. It happens to my same account from multiple computers.
Minecraft Crash Report ----
// There are four lights!
Time: 9/29/14 1:03 PM
Description: Batching chunks
java.nio.BufferOverflowException
at java.nio.DirectIntBufferU.put(Unknown Source)
at java.nio.IntBuffer.put(Unknown Source)
at civ.a(SourceFile:93)
at cop.a(SourceFile:98)
at coh.a(SourceFile:80)
at coh.run(SourceFile:38)
at java.lang.Thread.run(Unknown Source)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
– Head –
Stacktrace:
at java.nio.DirectIntBufferU.put(Unknown Source)
at java.nio.IntBuffer.put(Unknown Source)
at civ.a(SourceFile:93)
– Affected level –
Details:
Level name: MpServer
All players: 1 total; [cio['sefjwm'/370395, l='MpServer', x=-3836.70, y=58.33, z=3317.45]]
Chunk stats: MultiplayerChunkCache: 20, 20
Level seed: 0
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: -60.00,64.00,-40.00 - World: (-60,64,-40), Chunk: (at 4,4,8 in -4,-3; contains blocks -64,0,-48 to -49,255,-33), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 639184989 game time, 643277842 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Forced entities: 44 total; [adw['item.tile.dirt.default'/370602, l='MpServer', x=-3839.16, y=41.00, z=3331.75], cio['sefjwm'/370395, l='MpServer', x=-3836.70, y=58.33, z=3317.45], adw['item.tile.dirt.default'/370603, l='MpServer', x=-3839.94, y=42.00, z=3339.88], adw['item.tile.dirt.default'/370601, l='MpServer', x=-3838.78, y=42.00, z=3336.75], adw['item.item.dyePowder.black'/370606, l='MpServer', x=-3828.97, y=43.00, z=3338.31], adw['item.tile.dirt.default'/370604, l='MpServer', x=-3839.28, y=41.00, z=3328.19], adw['item.item.dyePowder.black'/370605, l='MpServer', x=-3828.38, y=41.00, z=3328.00], afw['Skeleton'/370660, l='MpServer', x=-3796.72, y=43.00, z=3342.47], aep['Creeper'/370658, l='MpServer', x=-3804.50, y=44.00, z=3337.41], aer['Enderman'/370659, l='MpServer', x=-3805.66, y=44.00, z=3340.88], agj['Zombie'/370656, l='MpServer', x=-3805.47, y=44.00, z=3339.81], adw['item.tile.dirt.default'/370568, l='MpServer', x=-3841.88, y=41.00, z=3327.91], adw['item.tile.dirt.default'/370399, l='MpServer', x=-3839.56, y=41.00, z=3327.03], adw['item.tile.dirt.default'/370569, l='MpServer', x=-3841.09, y=41.00, z=3327.44], adw['item.tile.dirt.default'/370398, l='MpServer', x=-3838.03, y=41.00, z=3327.81], adw['item.tile.stonebrick'/370570, l='MpServer', x=-3840.72, y=41.00, z=3320.13], adw['item.tile.dirt.default'/370397, l='MpServer', x=-3840.00, y=41.00, z=3326.25], adw['item.tile.dirt.default'/370571, l='MpServer', x=-3841.88, y=41.00, z=3320.91], adw['item.tile.stonebrick'/370396, l='MpServer', x=-3839.00, y=41.00, z=3322.94], adw['item.tile.dirt.default'/370572, l='MpServer', x=-3840.81, y=42.00, z=3339.78], adw['item.tile.dirt.default'/370573, l='MpServer', x=-3841.78, y=41.00, z=3332.28], adw['item.tile.dirt.default'/370574, l='MpServer', x=-3841.88, y=42.00, z=3339.88], adw['item.tile.dirt.default'/370575, l='MpServer', x=-3840.06, y=42.00, z=3335.06], adw['item.item.dyePowder.black'/370628, l='MpServer', x=-3822.47, y=41.00, z=3322.28], acl['Sheep'/370629, l='MpServer', x=-3808.88, y=69.00, z=3323.31], adw['item.item.dyePowder.black'/370630, l='MpServer', x=-3823.09, y=42.00, z=3333.41], acl['Sheep'/370563, l='MpServer', x=-3853.41, y=67.00, z=3310.81], adw['item.tile.stonebrick'/370564, l='MpServer', x=-3840.63, y=41.00, z=3325.28], acl['Sheep'/370625, l='MpServer', x=-3816.56, y=63.00, z=3306.03], adw['item.tile.stonebrick'/370565, l='MpServer', x=-3841.38, y=41.00, z=3321.69], acl['Sheep'/370626, l='MpServer', x=-3816.53, y=66.00, z=3309.75], adw['item.tile.stonebrick'/370566, l='MpServer', x=-3841.88, y=41.00, z=3323.91], adw['item.tile.dirt.default'/370567, l='MpServer', x=-3841.00, y=41.00, z=3323.31], adw['item.item.dyePowder.black'/370627, l='MpServer', x=-3823.75, y=41.00, z=3326.38], acl['Sheep'/370652, l='MpServer', x=-3793.94, y=75.00, z=3327.34], afw['Skeleton'/370651, l='MpServer', x=-3800.00, y=21.00, z=3314.50], adw['item.tile.dirt.default'/370577, l='MpServer', x=-3840.72, y=42.00, z=3333.75], adw['item.tile.torch'/370576, l='MpServer', x=-3840.88, y=42.00, z=3335.63], adw['item.tile.dirt.default'/370579, l='MpServer', x=-3841.88, y=42.00, z=3333.66], adw['item.tile.dirt.default'/370578, l='MpServer', x=-3841.38, y=41.00, z=3329.13], adw['item.tile.dirt.default'/370581, l='MpServer', x=-3840.72, y=42.00, z=3337.34], adw['item.tile.dirt.default'/370580, l='MpServer', x=-3841.78, y=41.00, z=3331.06], adw['item.tile.torch'/370583, l='MpServer', x=-3840.13, y=63.50, z=3329.47], adw['item.tile.dirt.default'/370582, l='MpServer', x=-3840.19, y=42.00, z=3335.88]]
Retry entities: 0 total; []
Server brand: vanilla
Server type: Non-integrated multiplayer server
Stacktrace:
at cen.a(SourceFile:308)
at bsu.b(SourceFile:2252)
at coh.run(SourceFile:44)
at java.lang.Thread.run(Unknown Source)
– System Details –
Details:
Minecraft Version: 1.8
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.6.0_26, Sun Microsystems Inc.
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Sun Microsystems Inc.
Memory: 67945256 bytes (64 MB) / 236244992 bytes (225 MB) up to 1060372480 bytes (1011 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
Launched Version: 1.8
LWJGL: 2.9.1
OpenGL: ~ERROR~ RuntimeException: No OpenGL context found in the current thread.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
Using VBOs: No
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (US)
Profiler Position: N/A (disabled)
I haven't posted for a while now but one aspect of this defect seems to have been fixed a while back with how the .dat files were being read. This was the issue where people on a server moving into new chunks would kick all players with this error. I've done a lot of exploring recently and this doesn't seem to happen anymore. Unfortunately this error shows for a multitude of reasons and the others seem to still be happening to people.
Arkov that is completely different. For most laptops by default, closing the screen also disconnects your Internet. Disconnecting your Internet will cause you to lose connection to your Minecraft server >.>
How beefy of a server would we need then? Like I mentioned earlier we are running on a ram disk and have 16 GBs of ram on the server and it never even uses more than a couple GBs on full load. The server is on a 250 down 60 up line. Some of our users are connecting on fiber so that should be plenty good for Minecraft. Even with just one person on as soon as they move to a new chunk it crashes.
Andrew I believe that triggers the same error but for a different reason. I've this same error message when overloading the server with infinite villagers or tons of redstone but I think it's different. You can trying using commands to move your character somewhere else to see if you are just overloading things.
They mean they can't directly do anything about it. I work in software QA and we have similar problems when using software pieces or libraries made by a 3rd party. If there is a flaw in netty (which it's sounding like the main issue) and not in the implementation of netty there isn't anything Mojang can do directly to fix the problem. Instead they have to either change how they use netty, go back to not using netty, or pressure the people making netty to fix their own problems. This sort of thing is quite common in software development though it is a bit strange this is taking so long for a solution to be determined.
We are seeing similar to what Kyle is explaining. On a brand new server we don't see it very often. On a server that had pre-1.7 terrain we get this every time someone goes off to explore new chunks. If everyone stays in already loaded chunks we see it rarely. It does not seem to be related to player connection to the server as the entire server gets kicked no matter who is exploring new chunks. We have 16 GBs of ram on the server and the entire server is inside a ram disk to try and increase performance. Under full load the server rarely uses more than a couple GBs of ram so it doesn't seem to be related either. We also will randomly see it other times but the error is so generic it's hard to tell what is really happening. All of these issue did not happen pre-netty implementation either.
Yes, that was spawned as a result of this report. Our server experiences no cpu or ram spikes like that. The dat file removals seem to have no affect either.
Ugh so many different issues with the same error muddying up this report. Early on this problem was with exploring new chunks. Now people are reporting stuff in Bukkit, mods, memory, the End and who knows what. Most people on my server have stopped playing since the first update causing this since they can't explore any new chunks. That was the main issue this report was for if I remember correctly.
It is pointless to post Bukkit stuff here as this is not the bukkit bug tracker.
Yeah, it's not the problem. I've seen single sheep escape pens. It may be more frequent with overcrowding but there is a defect at the root of the problem. Not sure why punching makes any difference. If the mob is out punching it just makes it run around.
No, the best way was how it worked before. Many people have machines already set up that use the position you land after leaving the cart trigger other things. There is no need to change things now.
My issue is it kicks everyone when exploring. If everyone stays in already generated chunks we can play for days no problem. As soon as anyone starts going into unexplored chunks everyone gets kicked every minute or so. This is not an exaggeration. It is every 1-2 minutes the server gets kicked. Once those previously new chunk have generated and people have been there for a while the server is again back to normal.
@Talven81 - we don't use the scoreboard and I can't find the dat file for it anywhere. I did a quick look through the other dats but all of them should be the normal ones required for basic play; map, level, uid, mineshaft, stronghold, etc...
This bug tracker is for vanilla Minecraft only. Spigot issues will have to be reported to spigot. Lots of things bring up this error message. Some are bugs, some are not. The original issue has long been fixed and this ticket is now a mess of other random issues. You would be better off reported new issues in their own tickets as this one will probably never get seriously looked at.