Kicked from server when opening my crafting grid - Payload may not be larger than 1048576 bytes
ProsperCraft opened this issue ยท 17 comments
Issue description:
I have a storage full of bees, and saplings from Forestry. Recently after adding more bees and saplings to it, I stated getting kicked when opening the crafting grid.
Steps to reproduce:
- breed lots of random bees, and trees
- insert them into the system
- keep adding until you can't open the system.
...
- Minecraft: 1.10.2
- Forge: forge-1.10.2-12.18.2.2123-universal.jar
- Refined Storage: refinedstorage-1.2.4.jar
Does this issue occur on a server? yes
May be related to this-
#195
raoulvdberge, would doing so reduce the amount of lag introduced to the system when you break power to your Controller and then reconnect? I have millions of items (lots in external Quantum Storage) and when I move my system or lose RF to it it tends to lag the server pretty badly.
No @EvilNotion that is related to #566
I just ran into this myself in 1.10.. supposedly a player queued up a big crafting task.
This is happening to me in SkyFactory 3 whenever i look at my disk drives/controller.
@fattness5 Update HWYLA, this is another issue.
We see the same error here at Sky Factory 3 with Refined Storage 1.2.18:
TranslatableComponent{key='disconnect.genericReason', args=[Internal Exception: java.lang.IllegalArgumentException: Payload may not be larger than 1048576 bytes], siblings=[], style=Style{...
(Log file)
Triggered here by ordering a large amount of items and using Ctrl
+ Shift
to force it to que it. We have multiple other autocrafting task running, but everytime we using the that feature, the server crashed.
We also see it after creating other smaller tasks, but that is not very often.
Why don't you update your SF3 instance before coming to the issue tracker? @exetico
@raoulvdberge - Oh, damn. I just forgot that my current setup didn't update the instance by itselves. Sorry for taking your time.
No problem, @exetico.
Never mind, this likely also belongs in #1790 -- Different location for this issue but in the end it comes down to the transport not supporting chunks / wanting to send it all at once
We did fix it by extracting all the tools and armour out of the system. There was a LOT in there. Because these don't stack (enchantments / varying levels of wear) they all show up as a separate item, likely making the item list massive.
Having this issue on ATM6 as well
"Payload may not be larger than 1048576 bytes" when opening the terminal. A lot of items such as armour are in our storage system, not sure if that matters?
@raoulvdberge or @way2muchnoise could you reopen this problem?