Tried to read nbt tag that was too big tried to allocate ошибка minecraft

[1.7.10] Tried to read NBT tag that was too big #1337

Comments

ghost commented Jul 2, 2016 •

When entering an area of the world, there is a period of lag and no messages are sent/received from the client, then they’re kicked with the message above.

I removed a few mods at a time and the issue seemed go away and re-appear after testing with and without Forestry.

Forge version: 10.13.4.1614
Forestry version: 4.2.13.61

The text was updated successfully, but these errors were encountered:

Nirek-K commented Jul 2, 2016

that is usually caused by having an item with an nbt tag that is too long, ie if you have bags inside of bags inside of bags of items.

ghost commented Jul 2, 2016 •

This is caused when a particular chunk is loaded. I’ve tried erasing the chunk with WorldEdit, but this didn’t help. I would assume deleting the region would probably fix it, but I’d rather not go to such drastic measures if possible.

mezz commented Jul 3, 2016 •

There doesn’t seem to be a good way to diagnose this issue.
If deleting the chunk did not fix the message, then you did not delete the right chunk.
If you can narrow down which tile is causing the problem I may be able to help, but unfortunately without that I can only guess at the situation.
Can you give another try to figuring out which chunk is causing the problem?

ghost commented Jul 4, 2016 •

I just ended up restoring an older version of the region. I’ll have a play around, but I’m 99% sure I deleted the correct chunk as well as neighbouring chunks (went in with a render distance of 2 from multiple directions to figure out which one it was). I’m using binnie patcher, so it could potentially stem from there/binnie’s mods affecting a Forestry machine or chunk/region data or something. I tried without binnie’s first and it still crashed, but maybe the data was still in the Forestry ‘whatever’ (seeing as I deleted the chunks I don’t know if a machine could have caused it, maybe the TE still existed, I don’t know).

Thanks for your time though. I’ll see if I can figure anything else out in the meantime.

CovertJaguar commented Jul 6, 2016 •

It’s possible using a NBT editor to find and remove specific NBT tags from your world.

It is however slightly tedious as you have to find the correct region file (.mca).

If you did that, you could in theory inspect the data directly and tell exactly what caused the error in the first place.

Minecraft Forums

I have a problem on my Minecraft 1.12.2 modded server, the server is running fine I play with my friend (2 players in the server) I once get killed by a mob I immediately get kicked from server and this appear. Picture

It says: tried to read NBT tag that was too big; tried to allocate: 2097153bytes where max allowed: 2097152

Now I keep getting this message every time when I try to join my server. Now I’m not able to join the server, my friend also.

The server was running fine, no lag. The only thing I have to do is deleting the world, but I’ve did that already and it happens again.

After a while I deleted players data (me and my friend data) from the world and restarted the server and we was able to join, we joined and when we go to the place where we died the same thing happens again.

Corrupted world, restore from backup.

Corrupted world, restore from backup.

I didn’t get any world backup. Here is my server’s folder: https://imgur.com/a/URoJT1x

And it didn’t came into your mind to make backups? I guess you didn’t care about that world.

And it didn’t came into your mind to make backups? I guess you didn’t care about that world.

I don’t know how I can do that although I generated a new world and after a while of playing the same thing happened when my friend died.

Do you have any mods that add gravestones? I’ve seen similar reports associated with such mods; for example. If deleting player data isn’t working you can try using MCEdit to go to the location you died and delete the gravestone (it will appear as a missing texture block with an unknown block ID; as long as there aren’t other modded blocks around it should be easy to find).

You could also try installing this mod, although you should be aware that it may cause worse problems if the issue is world corruption and not just a mod attempting to send too much data at once (it bypasses the packet size limit; either way, 2 MB is extremely large even for an entire chunk, which is normally less than 1/20 of that even when uncompressed).

Do you have any mods that add gravestones? I’ve seen similar reports associated with such mods; for example. If deleting player data isn’t working you can try using MCEdit to go to the location you died and delete the gravestone (it will appear as a missing texture block with an unknown block ID; as long as there aren’t other modded blocks around it should be easy to find).

You could also try installing this mod, although you should be aware that it may cause worse problems if the issue is world corruption and not just a mod attempting to send too much data at once (it bypasses the packet size limit; either way, 2 MB is extremely large even for an entire chunk, which is normally less than 1/20 of that even when uncompressed).

Yes, I’m using this gravestone mod. Now you made the issue easy for me, I’ll try to use MCEdit and check. Thanks a lot!

Tried to read NBT tag that was too big; tried to allocate: 2097216bytes where max allowed: 2097152 #3606

Comments

glepet1962 commented May 12, 2019 •

I have VanillaFix in modpack. It begins spamming this issue:

doing a /mc rs reset stops the issue temporarily

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

The text was updated successfully, but these errors were encountered:

Raycoms commented May 12, 2019

Does this issue return after a while again? After the rs reset?

glepet1962 commented May 12, 2019

Yes. After doing the rs reset, after 3-4 minutes it happened again. I was doing nothing but walking around the colony.

Raycoms commented May 12, 2019

@OrionDevelopment there seems to be a leak somewhere?

Nightenom commented May 12, 2019

Raycoms commented May 12, 2019

Because this only checks the size of the Request manager and not the size of the entire view.

Nightenom commented May 12, 2019 •

but it crashes on the read nbtcompound not whole bytebuf

Caused by: java.lang.RuntimeException: Tried to read NBT tag that was too big; tried to allocate: 2097216bytes where max allowed: 2097152
at com.minecolonies.coremod.colony.ColonyView.handleColonyViewMessage(ColonyView.java:579)

Nightenom commented May 12, 2019 •

The only possibility I can see is that colony.getRequestManager().reset() didnt somehow clear the rs

Nightenom commented May 12, 2019

@glepet1962 Can you send us the world?

glepet1962 commented May 12, 2019

update: I did another rs reset around 6:41 and have not had it happen since (now 7:40). I have been in the colony the whole time. I closed the game out during this time when I removed a couple mods, and then started up again. Not having any issues yet.
Maybe the first rs reset didn’t take, but the second did?
I’ve never sent a world, what file(s) would I need to send?

Nightenom commented May 12, 2019

OrionDevelopment commented May 12, 2019

As @Nightenom No idea how this happens since it should kill it self.
The reset can not not take, it overrides local fields directly by creating a new instance of the datastore manager, as well as new Central datastores and resolvers for retrying and Player so unless @glepet1962 can actually reproduce this again, I would put some money on: Something somewhere does something stupid

Comments

xenexelen commented Dec 2, 2018

Issue description: After remove and reinsert a Storage Modul in a Modular Storage (Because drawing-issues if you remove and insert many times things to a Storage Modul [i think for the drawing only the insert not the remove of something will be registeres]) i gettin a crash, after the crash, i cannot open the Storage Modul without the same error. «. Tried to read NBT tag that was too big; tried to allocate: 2097159bytes where max allowed: 2097152. «.

Steps to reproduce: It isn’t good to reproduce, i do this many times before i get the error. The Modular Storage contains one Storage Modul Level 3 with approx. 50 other full Storage Modul Level 3.

My full mod-list:
appliedenergistics2-rv6-stable-4.jar
BetterBedrockGenerator-1.12-6.1.1.jar
BiblioCraft[v2.4.5][MC1.12.2].jar
binnie-mods-1.12.2-2.5.1.184.jar
Born+In+A+Barn+V1.8-1.12-1.1.jar
buildcraft-core-7.99.19.jar
buildcraft-factory-7.99.19.jar
buildcraft-transport-7.99.19.jar
ChickenChunks-1.12.2-2.4.1.73-universal.jar
CodeChickenLib-1.12.2-3.2.2.353-universal.jar
CoFHCore-1.12.2-4.6.1.22-universal.jar
CoFHWorld-1.12.2-1.3.0.6-universal.jar
CraftTweaker2-1.12-4.1.13.jar
diethopper-1.1.jar
environmentalcreepers-1.12.2-1.4.0.jar
FastWorkbench-1.12.2-1.6.0.jar
FinderCompass-1.12.1.jar
forestry_1.12.2-5.8.2.374.jar
gravestone-1.10.1.jar
Guide-API-1.12-2.1.6-61.jar
Hwyla-1.8.26-B41_1.12.2.jar
InventoryTweaks-1.63.jar
ironchest-1.12.2-7.0.40.824.jar
jeibees-0.9.0.5-mc1.12.2.jar
jeiintegration_1.12.2-1.5.1.36.jar
jei_1.12.2-4.13.1.225.jar
journeymap-1.12.2-5.5.3.jar
JustEnoughResources-1.12.2-0.8.5.27.jar
mcjtylib-1.12-3.0.7.jar
moreoverlays-1.14-mc1.12.2.jar
MouseTweaks-2.9-mc1.12.2.jar
MTLib-3.0.5.jar
Neat+1.4-17.jar
netherbound-1.2.jar
NetherPortalFix_1.12.1-5.3.17.jar
OpenComputers-MC1.12.2-1.7.3.146.jar
Pam’s+ClaySpawn+1.12a.jar
Pam’s+Get+all+the+Seeds!+1.12a.jar
Pam’s+Llama+Milking+1.12.2b.jar
Pam’s+Sheep+Milking+1.12.2b.jar
RedstoneFlux-1.12-2.1.0.6-universal.jar
rftools-1.12-7.59.jar
rftoolsctrl-1.12-1.9.2.jar
SolarFluxReborn_1.12.2-4.16r.jar
starterkit-1.12.2-1.0.18.1.jar
ThermalDynamics-1.12.2-2.5.3.16-universal.jar
ThermalExpansion-1.12.2-5.5.2.39-universal.jar
ThermalFoundation-1.12.2-2.6.1.22-universal.jar
UniDict-1.12.2-2.9.1.jar
valkyrielib-1.12.2-2.0.18.3.jar
WanionLib-1.12.2-1.9.jar
Wawla-1.12.2-2.5.264.jar

Relevant logs, if any:

https://pastebin.com/rXTYfi9R
Search for «[08:50:42] [Netty Local Client IO #0/ERROR]»

The text was updated successfully, but these errors were encountered:

«Tried to read NBT tag that was too big» kick loop after mining stacked item filled shulker

Details

windows 10 home 64 bit
Java version 8 update 281

16gb ddr4 ram
intel core I7 6700hq
geforce gtx1070

jvm arguments of client profile:

latest-1.log = Server log
latest.log = Client log

Description

When you destroy a shulker containing stacked tools or other stacked things that have large nbt tags, your client disconnects from the server and displays this message:

«Internal Exception: io.netty.handler.codec.DecoderException:
java.RuntimeException: Tried to read NBT tag that was too big;
tried to allocare: 2097185bythes where max allowed: 2097152″

reconnecting to the server loads the world as usual, but disconnects again after a fraction of a second in game. This results in a «quasi ban» and also affects everyone loading the area afterwards.

How to recreate:

1. Use something like NBT Explorer or the the «/more» command on a paper server with essentials installed to create a shulker full of stacked and enchanted items that you normally couldn`t stack. Now get that shulker into your creative saved toolbar.

2. Log into any minecraft server above 1.12.2.

3. Get the modified shulkerbox from your creative saved toolbar and place it on the ground.

4. Go into gamemode survival and break the Shulkerbox. After that you get kicked and get the error message. (no problem breaking it in creative)