Harley Falkoff
- kinnichi
- kinnichi
- America/Havana
- Yes
- No
MC-292
When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with and Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following error:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East.
Steps to Reproduce:
1. Connect a piston to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.
Put your operating system (Windows 7, Windows XP, OSX) and Java version if you know it here
Ubuntu
When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with and Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following error:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East.
Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.
When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with an
dInternal Exception error.What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following error:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East.
Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.
When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with an Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the followingerror:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East.
Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with an Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following client side error message:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
The server gets the following error:
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East.
Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.
When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with an Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following client side error message:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
The server gets the following error but the IO # varies:
[Server] Netty Epoll Server IO #13/ERROR io.netty.util.IllegalReferenceCountException: refCnt: 0
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East.
Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.
When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with an Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following client side error message:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
The server gets the following error but the IO # varies:
[Server] Netty Epoll Server IO #13/ERROR io.netty.util.IllegalReferenceCountException: refCnt: 0
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East. May require extra repeaters at different delays.
Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.
When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with an Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following client side error message:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
The server gets the following error but the IO # varies:
[Server] Netty Epoll Server IO #13/ERROR io.netty.util.IllegalReferenceCountException: refCnt: 0
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East.
May require extra repeaters at different delays.Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.When many pistons fire on the same game tick on a multiplayer server, there is a chance that at least one player will be kicked with an Internal Exception error.
What I expected to happen was...:
I created a farm where chickens lay eggs and drop them into a hopper with a comparator that triggers 24 pistons to harvest sugar cane and pumpkins.What actually happened was...:
About 1 in every 3 fires of the pistons causes a small portion of the players on the server, in render distance, to be kicked from the server with the following client side error message:Internal Exception: io.netty.handler.codec.DecoderException: Java.lang.IndexOutOfBoundsException: readerIndex(16) + length(7868) exceeds writerIndex(16): UnpooledHeapByteBuf(ridx: 16, widx, 16, cap: 16)
The server gets the following error but the IO # varies:
[Server] Netty Epoll Server IO #13/ERROR io.netty.util.IllegalReferenceCountException: refCnt: 0
A screenshot (attached) taken between the pistons firing and fully extending, thus kicking the player, shows double piston heads.
Using fewer pistons when running the device causes the same issue at a lower rate, which makes it seem as though it's a once in a great while error with one single piston. This occurs even when triggered by a lever, rather than an egg in the hopper. This does not seem to occur with pistons facing up or West. Tested using pistons facing East. It also seems to only occur when a second repeater other than the one directly against the piston is added to the redstone circuit.
Steps to Reproduce:
1. Connect a piston facing East to a redstone clock on a multiplayer server.
2. Wait for the piston to kick the player. Connect more pistons to the clock to kick the player faster.
I have had similar experiences, and yes, even an unremarkable flat wall will do that.
Wouldn't that be better suited for the official forums than this bug tracker? Also, this seems to be in the same spirit as the Block Update Detectors and is likely to be left in intentionally.
I've had this issue and it seems to be related to having a slow or occupied processor on the client or server side. It happened to me in 1.2.5 when I was hosting the server in use as well as running Minecraft.exe on the same computer but at the time I had several other programs open that were using up my RAM and processor power. I now run minecraft with little else open and no longer have this issue.