"[SEVERE] Item entity # has no item?" is spammed in the console and items appear as stone for invalid IDs or on initial drop
The Server is spammed with Item entity number has no item!? until it crashes. ~~It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}
Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!
Marcono says:
Like I wrote already, the problem is the getEntityItem() method (MCP 1.8 name). Minecraft expects it to be null when no item data is stored but this method is required to return an ItemStack for rendering (else the client will crash). Because of this currently it returns a new ItemStack if the stored ItemStack is null (and prints the "Item entity # has not item?!" error message).
Linked Issues
is duplicated by21
MC-31287Minecraft client complains about missing itemsDuplicateMC-35821FishingDuplicateMC-35967Random freezingDuplicateMC-36798Constant spam of Item entity xxx has no Item on clientconsoleDuplicateMC-40610Summon Item causes FPS dropDuplicateMC-40625Client ErrorDuplicateMC-46230World don't have items, and crash when villager tradeDuplicateMC-64255Game Log strange error "item entity 5442890 has no item?!"DuplicateMC-65213Client thread/ERRORDuplicateMC-65798Client thread/ERRORDuplicateMC-66893Console spammed when I'm not a lan host onlyDuplicateMC-67772Log spamDuplicateMC-70170"Entity 12101 has no item?!" error messageDuplicateMC-71837Harvested Wheat Briefly Shows as Stone DuplicateMC-72746[Client thread/ERROR]: Item entity 1574 has no item?!DuplicateMC-76462 [Client thread/ERROR]: Item entity xxxxx has no item?! causing lag/glitchy behaviour in SMP 1.8.1DuplicateMC-90754Clients launcher large number of spam [xx:xx:xx] [Server / Client thread/ERROR]: Item entity xxxxxx has no item?!DuplicateMC-91489Freezing Game Then Crashing, and disconnectDuplicateMC-93166Thrown potion entity # has no item?! spam.DuplicateMC-94184lg error??¿DuplicateMC-99954Invalid item entities without actual items exist.Duplicaterelates to4
MC-53439The top block of a two-block plant temporarily becomes a peony/sunflower upon placing a block in the bottomFixedMC-99914DataWatcher / EntityMetadata ID is based on the class load order ! Can cause many issues !FixedMC-111978Item entities turn invisible when dropped on the groundAwaiting ResponseMC-93454Dropped Items are shown as stone [Multiplayer]Duplicate
Created Issue:
Item entity *number* has no item is spammed in a sever consel till it crashes
The Server is spammed with item entity number has no item until it crashes. It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Attachments2
crash-2013-03-14_20.48.41-server.txt
Item entity*number*has no item is spammed in a sever consel till it crashes"[SEVERE] Item entity # has no item?" is spammed in a sever consel till it crashes
is duplicated by
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
The Server is spammed with item entity number has no item until it crashes. It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!
"[SEVERE] Item entity # has no item?" is spammed in a sever conseltill it crashes"[SEVERE] Item entity # has no item?" is spammed in a sever console till it crashes
is duplicated by
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
is duplicated by
Confirmed for 14w31a
My client log is full of "[Client thread/ERROR]: Item entity X has no item?!": over a couple of hundreds of these messages.
I was playing on a server.
is duplicated by
is duplicated by
is duplicated by
duplicates
is duplicated by
duplicates
is duplicated by
relates to
is duplicated by
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
duplicates
duplicates
duplicates
duplicates
duplicates
duplicates
The Server is spammed with item entity number has no item until it crashes. It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!
From Marcono1234:
The reason for this bug in 1.8 (recompiled with MCP): (Please add this completely or partwise to the description)
When the getItemEntity() method is called and the value of the Item tag is null (does not exist or stores the value null), it prints the error message and return a new ItemStack however it does not modify its own Item tag. This means that the next time the method is called it will print again the error and so on. A possible fix would be to also set the returned ItemStack as item stack of the item entity.Possible fix (1.8 using MCP)/** * Returns the ItemStack corresponding to the Entity (Note: if no item exists, will log an error but still return an * ItemStack containing Block.stone) */ public ItemStack getEntityItem() { ItemStack var1 = this.getDataWatcher().getWatchableObjectItemStack(10); if (var1 == null) { if (this.worldObj != null) { logger.error("Item entity " + this.getEntityId() + " has no item?!"); } ItemStack defaultItemStack = new ItemStack(Blocks.stone, 1); this.setEntityItemStack(defaultItemStack); return defaultItemStack; } else { return var1; } }Eventually the contructor of the EntityItem class should be changed as well to make sure that always a non-null value is set as EntityItemStack. (In my tests that did not work very well)
is duplicated by
The Server is spammed with item entity number has no item until it crashes. It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!
From Marcono1234:
The reason for this bug in 1.8 (recompiled with MCP): (Please add this completely or partwise to the description)
When the getItemEntity() method is called and the value of the Item tag is null (does not exist or stores the value null), it prints the error message and return a new ItemStack however it does not modify its own Item tag. This means that the next time the method is called it will print again the error and so on. A possible fix would be to also set the returned ItemStack as item stack of the item entity.Possible fix (1.8 using MCP)/** * Returns the ItemStack corresponding to the Entity (Note: if no item exists, will log an error but still return an * ItemStack containing Block.stone) */ public ItemStack getEntityItem() { ItemStack var1 = this.getDataWatcher().getWatchableObjectItemStack(10); if (var1 == null) { if (this.worldObj != null) { logger.error("Item entity " + this.getEntityId() + " has no item?!"); } ItemStack defaultItemStack = new ItemStack(Blocks.stone, 1); this.setEntityItemStack(defaultItemStack); return defaultItemStack; } else { return var1; } }Eventually the contructor of the EntityItem class should be changed as well to make sure that always a non-null value is set as EntityItemStack. (In my tests that did not work very well)
Please remove the provided fix as like [Mod] redstonehelper said getter methods are not supposed to change attributes of a class
is duplicated by
The Server is spammed with item entity number has no item until it crashes. It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!Marcono says:
Like I wrote already, the problem is the getEntityItem() method (MCP 1.8 name). Minecraft expects it to be null when no item data is stored but this method is required to return an ItemStack for rendering (else the client will crash). Because of this currently it returns a new ItemStack if the stored ItemStack is null (and prints the "Item entity # has not item?!" error message).
Can you include the comment above please?
is duplicated by
The Server is spammed with
item entitynumberhas no itemuntil it crashes. It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!Marcono says:
Like I wrote already, the problem is the getEntityItem() method (MCP 1.8 name). Minecraft expects it to be null when no item data is stored but this method is required to return an ItemStack for rendering (else the client will crash). Because of this currently it returns a new ItemStack if the stored ItemStack is null (and prints the "Item entity # has not item?!" error message).
The Server is spammed with Item entity number has no item!? until it crashes. It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!Marcono says:
Like I wrote already, the problem is the getEntityItem() method (MCP 1.8 name). Minecraft expects it to be null when no item data is stored but this method is required to return an ItemStack for rendering (else the client will crash). Because of this currently it returns a new ItemStack if the stored ItemStack is null (and prints the "Item entity # has not item?!" error message).
is duplicated by
is duplicated by
relates to
relates to
is duplicated by
"[SEVERE] Item entity # has no item?" is spammed in a sever console tillit crashes"[SEVERE] Item entity # has no item?" is spammed in a sever console until it crashes
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
The Server is spammed with Item entity number has no item!? until it crashes. ~~It is the spawners because it stops when i break them. The spawners are custom and spawn armour and weapons. A copy of the spawner is in the attachments and a crash report.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Client> [02:10:41] [Client thread/ERROR]: Item entity 9740 has no item?!Marcono says:
Like I wrote already, the problem is the getEntityItem() method (MCP 1.8 name). Minecraft expects it to be null when no item data is stored but this method is required to return an ItemStack for rendering (else the client will crash). Because of this currently it returns a new ItemStack if the stored ItemStack is null (and prints the "Item entity # has not item?!" error message).
"[SEVERE] Item entity # has no item?" is spammed ina severconsoleuntil it crashes"[SEVERE] Item entity # has no item?" is spammed in the console and items appear as stone for invalid IDs or on initial drop
relates to
is duplicated by
relates to
Mounting and riding horses works fine here, unable to reproduce. For the item issue, see MC-11834.
this probably has something to do with MC-31688
I don't know why this happens either, I have a decent computer and I used to have around 170 fps in a normal world, but now I get around 70fps with huge fps drops.
Though I got this problem in 13w38 now it also happens to me in 13w37
oh never mind I found what my problem was already: MC-11834
yeah I had the same but for me it kept counting upwards until I had 3000 or something.
I think I figured out already what my problem is, it's MC-11834 it has nothing to do with this bug
ok never mind, I just realized MC-11834 this is my problem
Client> 13:18:40 Client thread/ERROR: Item entity 18616 has no item?! Client> 13:18:40 Client thread/ERROR: Item entity 18616 has no item?!
Duplicate of MC-11834
[09:07:15 INFO]: Client> [09:07:15] [Client thread/ERROR]: Item entity 611 has no item?!
This is a duplicate of MC-11834. Please use the search function to check before posting in the future. If you could not find the original report, please comment with the keywords you searched for.
OK Thanks, I look for a duplicated, but looks like I was not skilled enough to find it.
I will watch MC-11834 for resolution. The world I had was almost 6 months old with millions of items now gone.
Duplicate of MC-11834
When harvesting wheat, it occasionally shows as smooth stone blocks instead of wheat, for a brief instant.
I'm suspecting it MIGHT be related to MC-11834, since I got the errors at the same time as these harvestings, but I can't be sure. Could it just be a general error of breaking blocks and the wrong things coming out briefly, whether visible or not?
EDIT: This also happens with sugarcane occasionally, and breaking Lilacs sometimes briefly show up as Peonies. This may have already been submitted, will check. I know something like this was present in the snapshots when breaking grass; it might be a duplicate or related.
EDIT 9/16 - This may be a duplicate of MC-53439, just a different object due to block type.
I've noticed that this error seems to coincide with breaking of blocks. I wonder if the wrong items are coming out when blocks are broken. I've reported another error, where I noticed the coincidence: https://bugs.mojang.com/browse/MC-71837
Broken wheat briefly showed up as smooth stone. And the errors contained here happened around the same time. Perhaps it's not always visually possible to see the bug happening, but maybe the errors contained here (MC-11834) are being thrown BECAUSE of the bug contained in MC-71837.
Just a guess.
A similar occurrence I reported was breaking wheat changing into a smooth stone for a split second sometimes, on Survival Multiplayer on a vanilla server.
I wonder, does anyone else have MC-11834 happening around the time this happens to them (the "has no item" error)? Could the two be connected? It seemed to coincide for me.
Dupe of MC-11834
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
This issue reproduces way different from MC-11834
It is eventually the same.
- Game creates air item (
MC-90635) - (After reloading, estimated) Game notices that Item tag is invalid and removes it or does not load it at all
- The item has no Item tag (
MC-11834)
Edit: As you said it is a "follow-up" so you should anyways add the information to MC-90635 and additionally the title / summary of this report should contain the fact that it is caused by frosted ice
Caused by spamming the console with
[22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Server thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Server thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?! [22:27:50] [Client thread/ERROR]: Item entity 1608250 has no item?!
thus, duplicate of MC-11834
It works but it constantly prints the error message described in MC-11834
I saw this happen on a server once on 1.9-pre1. A server restart fixed it. Is this related to MC-11834?
This is the cause of MC-11834.
duplicate of MC-11834, if you have not, please use the search function in the future
Item entities turn invisible when dropped on the ground. The problem is intermittent, and I haven't found a way to reliably reproduce it. It doesn't seem to matter where the item entity comes from.
I've had items turn invisible both when tossing them out of my inventory and when being dropped from broken blocks.
It doesn't seem to matter what the item is. I've had it happen with seeds, lily pads and shulker boxes. The shulker boxes are especially worrying, because one invisible shulker box can result in the loss of a lot of valuable materials.
Code analysis. This bug is a continuation of MC-11834, and also a race condition, so it's hard to consistently reproduce. One way to force it to happen is to set a breakpoint in the entity metadata packet handler, and then resume the main thread. This can be a bit awkward to set up, though:
- Set up and start a server (superflat is the easiest). Disable mob spawning, and kill all entities (due to
MC-51732this will need to be repeated a few times to eliminate slimes). - Add -agentlib:jdwp=transport=dt_shmem,address=minecraft,server=y,suspend=n to the client JVM arguments.
- Launch the client.
- Open a command line, and run jdb -attach minecraft.
- In JDB, type threads and verify that (java.lang.Thread)0x1 Render thread running appears (that "Render thread" has ID 1).
- Connect to the server, and wait a few seconds.
- In JDB, type stop at ra:11 (where ra is ClientboundSetEntityDataPacket as of 1.16.4-pre1, and line 11 is handle). Note that this means that any entity metadata change will trigger the breakpoint, which includes sneaking and sprinting. If this is accidentally triggered, you will need to run resume several times.
- Spawn an item. This can be done by breaking a block or tossing an item in your inventory. Make sure that the item will land far enough away that it won't be picked up immediately.
- The game will freeze with the breakpoint hit in thread=Netty Client IO #2 (or similar).
- Type resume 1 in JDB to resume the render thread (which should advance one frame and then freeze again, or may unfreeze the game completely). This specifically needs to be done to ensure the item gets ticked before entity metadata is received, and is what actually reproduces the race condition.
- After a second, type resume to resume all threads. JDB will immediately say that the breakpoint was hit in thread=Render thread; type resume a second time to resume it.
- There will now be an invisible dropped item. Walking into it will still add it to the inventory.
Very belated, but I can say with certainty that this was caused by MC-11834, specifically the workaround for null items being them rendering as stone.
x10A94 over on #mcdevs experienced a similar issue (albeit with a modded setup, when writing a proxy server). This ended up being this issue, and while we did not find an exact set of steps to reproduce on vanilla, we did find a way to consistently cause it in a modded case. The specific information is in logs #177 (starting at 2019-03-09 22:50:48) and #178.
This bug is a continuation of MC-11834, as it now behaves after 16w32a (the first 1.11 snapshot). Where before, "Item entity #### has no item" would have been logged, now the item is removed. This happens both clientside and serverside.
public void tick() { if (this.getItem().isEmpty()) { this.remove(); } else { // actual tick } }
I think the intent of this code is partially to reject invalid items (but the same thing exists in the NBT loading code...). However, this can also be hit if the item is ticked after it has spawned, but before the associated metadata has been sent. For whatever reason, the spawn object packet does not include entity metadata in it, despite the fact that the spawn mob packet does. This means that, to properly spawn an item entity, the game must first send a spawn object packet, and then immediately after that send an entity metadata packet to actually set the item.
However, if the metadata packet hasn't arrived yet, the item is initially empty. Before, this would have led to the item rendering as stone and the log receiving 1 message each time the item renders (I think, might be each time it ticks), since the game detected the empty case within getItem and returned stone explicitly (the same check to remove items actually existed then, but it would never trigger because of stone). Now, the item is just removed.
How can you actually get the spawn object packet without the metadata packet, given that they're always sent one after the other? Simple – latency or delay in processing! If one packet is sent over the network completely, but then you get some lag and the other one takes a little while to arrive, they'll still arrive in order... but there's enough time for the client to tick after the spawn packet is received but before the metadata one happens. It's a fairly simple race condition. This can be forced by manually adding some extra delay to the entity metadata packet (e.g. a Thread.sleep(200) call in SPacketEntityMetadata.processPacket), and it was confirmed that this could be reproduced consistently in the case of the proxy if the packet is always delayed. However, without such modifications, it's completely up to lag whether or not it will happen and it's likely to be very rare except for on a very bad connection. (The proxy case had it happen more frequently due to buffering, but that's out of scope).
The pickup animation
There is one other weirdness: the item pickup animation actually still works! This can be seen in a video (recorded with the proxy) at around 15 seconds in. Note that for normal drops, the "All" value on F3 goes to 4 and then back to 3 when it's collected (and P is 1 in the collect animation), but for the missing item, All does not change while P still does. To understand why this is weird, recall that the collect item packet uses entity IDs; it doesn't send a complete copy of the item but instead assumes that the client already has a reference to the item. Also note that internally, the item pickup animation is a particle, hence the P value.
What's happening there is that the item's own call to remove doesn't fully remove it. It instead sets the removed flag to true, which is processed in World.tickEntities:
public void tickEntities() { // ... all sorts of stuff ... this.profiler.endStartSection("regular"); for (int i1 = 0; i1 < this.loadedEntityList.size(); ++i1) { Entity entity2 = this.loadedEntityList.get(i1); // ... ticking and riding stuff this.profiler.startSection("remove"); if (entity2.removed) { int l1 = entity2.chunkCoordX; int i2 = entity2.chunkCoordZ; if (entity2.addedToChunk && this.isChunkLoaded(l1, i2, true)) { this.getChunk(l1, i2).removeEntity(entity2); } this.loadedEntityList.remove(i1--); this.onEntityRemoved(entity2); } this.profiler.endSection(); } // ... all sorts of stuff ... }
This includes a call to onEntityRemoved, which for WorldClient is this:
protected void onEntityRemoved(Entity entityIn) { super.onEntityRemoved(entityIn); // Responsible for notifying IWorldEventListener instances if (this.entityList.contains(entityIn)) { if (entityIn.isAlive()) { // i.e. !entityIn.removed this.entitySpawnQueue.add(entityIn); // This seems odd, but it won't apply here so pretend it doesn't exist } else { this.entityList.remove(entityIn); } } }
This removes the item from WorldClient.entityList (appears in crash reports as "Forced entities", at least until 1.14) and World.loadedEntityList (which controls the All value in F3), and also the chunk. However, it doesn't touch World.entitiesById, and that's what the collect item effect uses. The fact that an entity can be left in one of these collections seems a bit broken (it's a bit of a memory leak if it could happen in actual cases) but I'm not sure what really should be done about it or if other things are affected. I also don't know if that leak still exists in 1.14; I've seen that the entity lists are different.
Fix and a bit more history
The fix is rather simple: just include entity metadata in the spawn object packet, like with spawn mob. This would make it impossible for the entity to exist before the metadata has been received (if something breaks up in the middle of the packet, the game will wait for the full packet to be received). Given that 1.14 already did some cleanup of the spawn object packet, it would make sense to clean up more of the weirdness here.
Funilly enough, this wasn't an issue in the distant past; there originally was a distinct spawn dropped item packet that included the item in it. This was changed to entity metadata circa 1.4.6 (actually 12w50a), presumably so that information about the item could be changed after it was spawned (e.g. MC-1347). This was also when the "Item entity #### has no item?!" logging and returning of stone were added, as well as the remove check that wouldn't have been – my guess is that empty items would rarely cause crashes before those checks were added and the checks were added to attempt to sidestep things that were hard to reproduce.
SpaghettiGoat, the issue you're experiencing is presumably something else – possibly MC-90683 but I'm not 100% sure.
You should - at least when you make such experiments - start Minecraft with the default launcher to allocate enough memory.
your JVM has only 256 MB - that is way too less.
Why is this closed as invalid? I'm able to reproduce it, sans the crashes. As item spawners are a vanilla feature, they should not be spamming the console like this.
EDIT: I should note, OP's crash report seems to indicate a mod item, "CrimTopaz", outside the ordinary item ID range.
On the other hand, I am getting messages of the form
with legitimate, vanilla-supported item spawners. The number just keeps incrementing; I've had it climb into the millions before. It makes traversing the server.log tedious. It also makes it difficult to communicate with players via the console; their chat and your own quickly get shunted off the screen.
So, what's the bug ? The crash or spamming of the console ?
Crash : Invalid because of too less memory
Spamming: Please provide exact steps to reproduce.
I've added a new schematic in case OP's schematic did not work.
Steps to reproduce:
where # is a number which continuously increments.
Can the description be updated and this be reopened? It's a real bug. Unless nobody else can reproduce it? I've had it on several servers on different computers.
Reopened.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
I can confirm it for 1.5.2, but haven't had a chance to test it on snapshots yet.
I can confirm this message is occurring in vanilla 13w19a. I just closed my game after playing for about an hour and saw this message in the new launcher window I didn't close when I started. It occurred about 20 times near the start of my game. All I did during the game was dig a fort, place a furnace and used it, placed some chests and used them, and made a farm. I can't recall what I was doing at the exact time the messages were spammed though. These messages are the only ones out of the ordinary inbetween the saving messages from pausing the game. It's possible it was the furnace I used and this message was when a fuel was still burning without items.
@Kanegasi : Did you just get this message or did Minecraft crash ? Either way, can you attach the relevant parts of output-client.log and output-server.log ?
Oops, didn't know the file comment was an actual comment. Anyways, no crash, I simply noticed the log entries after exiting my session and was curious and searched the tracker and then found this bug entry. Just thought I would share my experience.
I can confirm this bug with the Snapshot 13w23b Server. My world has a couple custom spawners, which from all accounts seem to be causing the issue, and severely lags the server. However, there are no such issues playing the same world in SinglePlayer. The server.log is posted above.
Snapshot 13w23b Server.log File
Bug Confirmed for Snapshot 13w24b
Confirmed for Snapshot 13w25b
The server.log file for 13w25b
I looked a bit further into the issue. For each of the custom spawners in my world, it outputs the error message twice. The message also appears to be coming from both the spawner blocks and spawner minecarts.
Another update. I found this in the development console of the Snapshot Launcher while working on the same map in singleplayer.
Client> 2013-06-20 16:10:40 [SERVER] [INFO] Saving and pausing game...
Client> 2013-06-20 16:10:40 [SERVER] [INFO] Saving chunks for level 'horse'/Overworld
Client> 2013-06-20 16:10:40 [SERVER] [INFO] Saving chunks for level 'horse'/Nether
Client> 2013-06-20 16:10:40 [SERVER] [INFO] Saving chunks for level 'horse'/The End
Client> 2013-06-20 16:28:28 [SERVER] [SEVERE] Item entity 414787 has no item?!
Client> 2013-06-20 16:28:28 [SERVER] [SEVERE] Item entity 414787 has no item?!
Client> 2013-06-20 16:29:09 [SERVER] [SEVERE] Item entity 431425 has no item?!
Client> 2013-06-20 16:29:09 [SERVER] [SEVERE] Item entity 431425 has no item?!
Client> 2013-06-20 16:30:26 [SERVER] [INFO] Saving and pausing game...
Client> 2013-06-20 16:30:26 [SERVER] [INFO] Saving chunks for level 'horse'/Overworld
Client> 2013-06-20 16:30:26 [SERVER] [INFO] Saving chunks for level 'horse'/Nether
Client> 2013-06-20 16:30:26 [SERVER] [INFO] Saving chunks for level 'horse'/The End
Client> 2013-06-20 16:30:46 [SERVER] [SEVERE] Item entity 469124 has no item?!
Client> 2013-06-20 16:30:46 [SERVER] [SEVERE] Item entity 469124 has no item?!
Client> 2013-06-20 16:30:50 [SERVER] [SEVERE] Item entity 470705 has no item?!
Client> 2013-06-20 16:30:50 [SERVER] [SEVERE] Item entity 470705 has no item?!
Client> 2013-06-20 16:30:58 [SERVER] [SEVERE] Item entity 474005 has no item?!
Client> 2013-06-20 16:30:58 [SERVER] [SEVERE] Item entity 474005 has no item?!
Client> 2013-06-20 16:31:01 [SERVER] [SEVERE] Item entity 475254 has no item?!
Client> 2013-06-20 16:31:01 [SERVER] [SEVERE] Item entity 475254 has no item?!
It did not, however, noticeably lag the game like it did in multiplayer.
Using 1.6pre, and also experiencing this issue. The launcher still shows the error messages in SP, but everything works fine. However, loading the map containing the Spawners in both LAN and Server MP results in a crash.
I am also experiencing this issue in 1.6.2.
Same outcome as HiFolksImAdam, the Development Console in the launcher shows the error messages in SP, but there's no noticeable performance loss.
Starting an MP server with the map works perfectly until a player logs in. The error messages are then printed to the console and memory usage then climbs to the max and the server crashes.
I believe that this has something to do with the unintended properties that we are using with the spawners, in my case, the manipulation of the t variable may be the issue (using seth blings structure spawner v2). However, I do not understand the issue while using the item entity spawner.
confirmed for 1.6.2 (except for the crashing) aren't you supposed to add some sort of tag to the item, currently I only give 'SpawnData' these tags:
-Age:5999
-Pos
You are supposed to add tags defining what type of item it is. However, this error still occurs regardless of what tags you add - even if you add every single tag an item could possibly have.
I can remember that this didn't happen with sethblings filter, but I might be wrong. I should try that sometime and then delete every tag one by one to see which one I should keep.
It happens with SethBling's filter too - even in his own maps. It didn't always happen, from what I remember, but now it happens for all item spawners.
If someone could go through an isolate each variable, we would be able to tell what is actually making the issue, not that it is just the spawners.
According to Gerrard it is not just one variable, it is caused by the fact that an item is spawned using a spawner and not dropped on the ground using q or breaking a block or killing a mob. Because when you use sethblings filter (which copies all the tags) you still get this message.
Got it. So this is an issue with the spawning of an item feature itself. It does allow for the item to be spawned in in that manner.
And that makes sense for the sethbling structure spawner v2 because if you go deep into the nbt tags, it does spawn an item entity (sandstone i believe, however i dont think that matters).
Confirmed for 1.6.2.
From what I can tell, the error is caused by the spawner itself, and not the entities it spawns. Or, more accurately, it occurs when the spawner tries to render an item spinning in its cage. It first constructs the entity without its item data, causing the error, and then fills in the missing SpawnData, which is why the issue occurs once per refresh of the spinning cage entity.
Hmm makes sense, but when it isn't active because there aren't players in the spawn range the item is still visible but It doesn't give the message. Can you explain that?
The message is generated every time the item in the cage needs to be refreshed. It needs to be refreshed any time it either successfully spawns at least one item, or fails to spawn an item because too many are nearby. It also needs to be refreshed when the chunk containing it is first loaded.
It should be noted that this message also spams the player's console, which is pretty annoying now that the launcher makes this visible in vanilla.
oh yeah that makes sense, basically ever time the spawner chooses a new entity in the 'spawnpotentials' list
This shouldn't be too hard to fix, I remember it didn't occur in 1.3
MOD PLEASE UPDATE STILL AN ISSUE IN 1.6.2
confirmed for 1.6.2
ok, now it really needs to be fixed, I had a ton of lag since the latest few snapshots and first I thought it was because of the antialiasing and stuff, but now I deleted all my spawners in my world and all of a sudden it's fixed. My memory goes up and up and up but without the spawners it stays around 100MB whereas it went all the way up to 3000MB first
Can this at least be marked confirmed for 1.6.4?
Cannot confirm that with vanilla Minecraft.
Is the affecting spawner placeable by a command ? (If yes, please provide the command)
Confirmed in 1.6.4. If you can, please update as confirmed.
*This only effects spawners, /summon doesn't create this problem
Also confirmed in 13w41b. Please update that as well, if my confirmation is reason enough to update the ticket. Thank you.
If a log is necessary to confirm, I can provide it.
Confirmed for 13w41b with the following command, in a command block:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:7,Damage:0,Count:1}}}Observe the spam in the Development Console of the launcher, or the server console if you perform this on a server.
The message is now of the form:
Here ya go.
I found a temporary workaround. I used item spawners everywhere to spawn items with age set to 5999 on top of a pressure plate to trigger redstone clocks. Because I don't want a laggy world caused by thousands of commands firing in one tick. So now I just made the spawner spawn XPOrb. Though sometimes you just want to spawn items. Then connect a command block to the pressure plate that spawns an xporb riding an item, that way the spawner still doesn't trigger the pressure plate as long as there are too many items near
Confirmed for 1.7.1.
It's worth noting that this will happen in an invalid dropped item from 1.6.4 is encountered in 1.7.1:
That spams and lags the server and clients until the item is collected. Fortunately, I think the item can still naturally despawn.
But yes, definitely confirmed for spawners as well.
it's not the items that cause lag. I have a world with about 50-100 different item spawners with age set to 5999 so they despawn immediately, even when I fly far far away from all the spawners so none of them is activated and I don't get error messages any more, I still have memory up to 2000MB and a lot of lag.
I'm getting the following log spam clientside on my purely vanilla SMP 1.7 server, no command blocks or edited in items. Haven't yet checked if it also occurs serverside. Doesn't seem to be causing server-side issues, but some people are complaining about occasional random severe stutters, which may or may not be related.
Note that all of the above messages are repeated multiple times.
I got this bug in Minecraft 1.7.2. I get a lot of this messages. It has so far not crashed my client so far. I am running linux version.
I really wonder what is causing this bug. It really breaks custom spawners. I think the idea about the entity rendering in the spawner is an excellent theory.
This really needs to be fixed. It comes from all sorts of spawners; I get the message even on spawners that do not spawn items.
This can be resolved by properly formatting your Summoned Item
/summon Item ~ ~2 ~
{id:1,Age:5900}(Stone with 10s of life - spews tons of Item Entity has no item?!
/summon Item ~ ~2 ~ {Item:
{id:1},Age:5900} (Stone with 10s of life - does NOT)
The difference between these two items is that the item spawned has a tag Item: Not FULLY sure why this resolves the issue, but it works for me.
That fix only works for summoned items, not spawners. For a perfectly-formatted spawner of any sort (so long as it can spawn items), it will have this error.
It would seem like spawners are suffering the same issue as an improperly formatted command if that is the case. So the issue could be in that it is not summoning an item properly.
I made a spawner of XPOrb riding an item, still the same message "Item entity # has no item?"
So this happens always that a Spawner tries to spawn an Item.
Command used:
/setblock ~ ~1 ~ minecraft:mob_spawner 1 replace {EntityId:XPOrb,SpawnData:{Value:0,Riding:{id:"Item",Item:{id:5,Damage:0,Count:1}}}}
sigh Confirmed in 1.7.4. Please. Please. PLEASE FIX THIS.
I am still getting this in snapshot 14w20b, but I don't think it has anything to do with the spawners, since I am on a vanilla world.
I am having the same issue in client/server, but instead of [SEVERE] it says:
[Client thread/ERROR]: Item entity # has no item?!
The server in question was running 14w18b. While I would like to move to 20b, but it actually causes more issues than it solves.
yeah I think the message is changed in the latest snapshot
I resolved this by a roll-back, but since have moved to 14w27b and found it far more agreeable than previous versions. It's worth a try.
Is this still happening in 14w28b?
Confirmed with default dungeon spawners (Skeleton and Zombie) in 14w29b.
I have this same issue on singleplayer in 14w32d and every 1.8 snapshot before and even 1.7.5 and later. i have plenty of ram and this issue consistently crashes my video driver (AMD 14.4) and which then causes any type of full screening on any program to take upwards of 10 seconds. It's pretty ridiculous, really. On multiplayer however, this issue does NOT crash the game but does spam the console.
*EDIT*
By fullscreening i mean, for example, opening or quitting minecraft or CS:GO or any other game for that matter
I still have this in 14w33a. I had this when I took a stone pressure plate from the creative menu.
Still present in the new 1.8 release. This happened during caving on SMP (vanilla, ultra hardcore rules). It kept changing the entity number.
[11:14:17] [Client thread/ERROR]: Item entity 383467 has no item?!
[11:14:17] [Client thread/ERROR]: Item entity 383467 has no item?!
[11:14:17] [Client thread/ERROR]: Item entity 383467 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:26:28] [Client thread/ERROR]: Item entity 405090 has no item?!
[11:32:08] [Client thread/ERROR]: Item entity 414574 has no item?!
[11:32:08] [Client thread/ERROR]: Item entity 414574 has no item?!
[11:32:08] [Client thread/ERROR]: Item entity 414574 has no item?!
[11:36:08] [Client thread/ERROR]: Item entity 425054 has no item?!
[11:36:08] [Client thread/ERROR]: Item entity 425054 has no item?!
[11:36:08] [Client thread/ERROR]: Item entity 425054 has no item?!
[11:47:20] [Client thread/ERROR]: Item entity 450031 has no item?!
[11:47:20] [Client thread/ERROR]: Item entity 450031 has no item?!
[11:58:13] [Client thread/ERROR]: Item entity 476488 has no item?!
[11:58:13] [Client thread/ERROR]: Item entity 476488 has no item?!
[11:58:13] [Client thread/ERROR]: Item entity 476488 has no item?!
[11:58:13] [Client thread/ERROR]: Item entity 476488 has no item?!
[12:07:56] [Client thread/INFO]: [CHAT] [name] was blown up by Creeper
[12:15:50] [Client thread/INFO]: Connecting to [ip]
[12:18:31] [Client thread/ERROR]: Item entity 12483 has no item?!
[12:18:31] [Client thread/ERROR]: Item entity 12483 has no item?!
[12:18:31] [Client thread/ERROR]: Item entity 12483 has no item?!
I've noticed that this error seems to coincide with breaking of blocks. I wonder if the wrong items are coming out when blocks are broken. I've reported another error, where I noticed the coincidence: https://bugs.mojang.com/browse/MC-71837
Broken wheat briefly showed up as smooth stone. And the errors contained here happened around the same time. Perhaps it's not always visually possible to see the bug happening, but maybe the errors contained here (
MC-11834) are being thrown BECAUSE of the bug contained inMC-71837.Just a guess.
While I play server-side (all vanilla), it doesn't seem to affect the server but my client log is spammed with "Item entity # has no item?!" every time I create a drop, either by mining or simply by dropping whatever. Maybe worth mentioning that I've made a clean install for 1.8, to see if it solves my lag issues. Well, it doesn't. Found out about this error instead.
Also having this issue on AMD video card, regardless of drivers. I've only received these bug reports twice, every other time it either freezes the computer screen, reboots the computer without errors (as if starting up for the first time), or crashes the computer (which is set to reboot, but it's registering as a crash and sending to me to the safemode options window). I've set it up to collect memory dumps on crash and I can't get Windows to register these crashes as an event (can't get a single memory dump out of it, kernel or otherwise).
Please fix! This renders the game unplayable.
http://gyazo.com/69b1aa4f07baf57a38f599795d26588d
Confirmed for 1.8.1
Hi All, new to this and MC in general, and made a duplicate of this issue, so sorry about that.
I am playing SMP on 1.8.1 with a friend, and I am having trouble everytime I activate doors using pressure pads, go through a portal, ride a horse etc. I lag out and sort of rubber band between different locations and my friend says I appear to be standing still. I get the following messages in my Game Output (see below), the times of which correlate to these laggy events.
I don't have any custom spawners or anything. Is there anything I can do or is this still not understood?
Cheers
[20:57:45] [Client thread/ERROR]: Item entity 45897 has no item?!
[20:57:45] [Client thread/ERROR]: Item entity 45897 has no item?!
[20:57:45] [Client thread/ERROR]: Item entity 45897 has no item?!
[20:57:45] [Client thread/ERROR]: Item entity 45897 has no item?!
[20:59:46] [Client thread/ERROR]: Item entity 56112 has no item?!
[21:12:53] [Client thread/ERROR]: Item entity 98369 has no item?!
Observed in 1.8.4 on client:
[12:12:48] [Client thread/ERROR]: Item entity 379481 has no item?!
vanilla, everything up to date, Item entity 863649 has no item?! and Item entity 873150 has no item?!
Cannot confirm for 1.8.6
/setblock ~ ~1 ~ minecraft:mob_spawner 0 replace {EntityId:Item,SpawnData:{Health:5,Age:0,Item:{id:bedrock,Damage:0,Count:1}}}The reason for the "Item entity # has no item?" error seems to be a missing or invalid Item id:
Cannot confirm for 1.8.7. Possibly patched?
I can confirm the command used does not cause the console to be spammed.
I can also confirm "/summon Item ~5 ~ ~" (relative co-ords to make sure you don't pick the item up) still spams the console on 1.8.7.
@Qi-rui Chen - By spams the console, do you mean it creates multiple messages when you run the command multiple times? And also, your summon command creating an error message is not a bug as you never assigned it an item while the command used elsewhere in this thread has a valid item.
After some more experimentation I can see what you mean @Noah Larkin.
Here is the results from testing version 1.8.7:
Singleplayer: The spawner does not cause anything to appear in the console, but "/summon Item" causes ~4 messages of "[Server thread/ERROR]: Item entity # has no item?!".
Singleplayer (open to LAN): Same as Singleplayer.
Multiplayer Server: The spawner does not cause anything to appear in the console, but "/summon Item" causes the server log to be spammed with "[<time>][Server thread/ERROR]: Item entity # has no item?!" and the client log to be spammed with "[<time>][Client thread/ERROR]: Item entity # has no item?!" (different value to server thread).
The server continues to be spammed if the player logs out from the server. The client still gets spammed upon joining the server. The spamming stops when the item is either picked up, despawns.
Stopping and restarting the server causes the spamming to stop.
Duplicate of
MC-12949– If you have not, please use the search function in the future, to see if your bug has already been submitted.For technical support, please use the Mojang Support Center.
— This action was performed automagically. If you believe this was done erroneously, please
raise an issue.
Duplicate of
MC-12949– If you have not, please use the search function in the future, to see if your bug has already been submitted.For technical support, please use the Mojang Support Center.
— This action was performed automagically. If you believe this was done erroneously, please
raise an issue.
Sorry for the bot spam.
I am not sure, but this issue does not look like
MC-12949at all.Yes, but the bot has some gears missing at the moment.
Still getting these messages in 15w36d
Bob: Before confirming more issues: You are aware there is 15w37a out already?
Opps. I didn't update my server as the devs warned 37a was buggy and forgot that 36d wasn't latest version anymore
The reason for this bug in 1.8 (recompiled with MCP): (Please add this completely or partwise to the description)
When the getItemEntity() method is called and the value of the Item tag is null (does not exist or stores the value null), it prints the error message and return a new ItemStack however it does not modify its own Item tag. This means that the next time the method is called it will print again the error and so on. A possible fix would be to also set the returned ItemStack as item stack of the item entity.
Eventually the contructor of the EntityItem class should be changed as well to make sure that always a non-null value is set as EntityItemStack. (In my tests that did not work very well)
Getter methods are not supposed to modify state.
You are right, I cannot quite figure out how exactly Minecraft creates items or what it is actually doing, however the readEntityFromNBT(NBTTagCompound tagCompound) method has a bug as the returned value of getEntityItem() is never null (If it would be null the client would crash because it could not render the item).
Here are some parts I don't understand:
Confirmed for 1.8.8
After the install of optifine...
Reports of modded versions of Minecraft are invalid, please try to reproduce it without any mods.
And also please don't paste the complete Game Ouput here. Saying that you can confirm it is enough as long as nothing changes for this bug.
Like I wrote already, the problem is the getEntityItem() method (MCP 1.8 name). Minecraft expects it to be null when no item data is stored but this method is required to return an ItemStack for rendering (else the client will crash). Because of this currently it returns a new ItemStack if the stored ItemStack is null (and prints the "Item entity # has not item?!" error message).
confirmed 15w47c
survival multi player on hosted server
windows 10 pro
java 1.8.0_66
log is absolutely flooded
Confirmed 15w49b
Btw that maybe caused by the little spinning entity in the spawner. I'm not sure.
Okay, so this may not help the multitude of server owners that are having this issue but maybe they can use this to track down their problem and get it fixed..
1) This problem can be caused by a plugin trying to spawn a non-spawnable item stack. IE a plugin tries to spawn Material.wall_sign or Material.melon_stem (there are a BUNCH more) these are items that players aren't "allowed" to hold thus they become invalid and typically get rendered as smooth stone when they are actually dropped in the world.
2) Every time one of these non-spawnable items gets "dropped" in the world it will cause this error at least once. Often times it will constantly spam until the offending item is picked up and /clear is run on the player holding the item.
3) If you have a plugin that spawns random items from minecraft into your world that is causing this problem contact the plugin's author and have them add this little bit of code to their plugin to fix the issue.
You must have essentials installed and the plugin will need to hook essentials. (the plugin guys know how to do this)
ItemStack is = new ItemStack(Material_To_Spawn);
MetaItemStack metaStack = new MetaItemStack(is);
{ //System.out.println("Unspawnable item: " + is.getType().name()); //do whatever they need to do, eg: return/continue/break etc. }if(!metaStack.canSpawn(theirplugin.getES()))
Confirmed for
I just had this in 1.9-pre2 by just dropping some items :\
Confirmed for
This came up a few times on singleplayer about an hour into playing a new singleplayer world in the 1.9 full release. I'm not exactly sure what to put here, but here's a paste of what my launcher said while I was playing:
[20:27:04] [Client thread/ERROR]: Item entity 18391 has no item?!
[20:27:04] [Client thread/ERROR]: Item entity 18391 has no item?!
[20:27:28] [Client thread/ERROR]: Item entity 18569 has no item?!
[20:27:28] [Client thread/ERROR]: Item entity 18569 has no item?!
I'm pretty sure this happened only while I was just mining some gravel, coal or iron. I've searched around for this issue and it seems to possibly be from when item entities stack together.
Just a note, this was in completely vanilla minecraft, no add-ons/mods or server plugins, just plain vanilla singleplayer.
Happens for me too in 1.9 release. Doesn't seem to affect anything, but I think these may be causing the split-second lag spikes I kept getting.
[14:55:08] [Client thread/ERROR]: Item entity 902073 has no item?!
[14:55:08] [Client thread/ERROR]: Item entity 902073 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:56:21] [Client thread/ERROR]: Item entity 903762 has no item?!
[14:57:12] [Client thread/ERROR]: Item entity 905420 has no item?!
[14:57:12] [Client thread/ERROR]: Item entity 905420 has no item?!
[14:57:56] [Client thread/ERROR]: Item entity 906896 has no item?!
[14:57:56] [Client thread/ERROR]: Item entity 906896 has no item?!
[15:20:45] [Thread-5/ERROR]: Error in class 'LibraryLWJGLOpenAL'
[15:20:45] [Thread-5/ERROR]: Source '1e574f1e-f745-4e41-866e-b4addffe496c' not found in method 'play'
My friend @The Papa says he experienced this issue in all of the 1.9.1 pre-releases in singleplayer. He reproduced it by blowing up lots of TNT in a world.
this issue appears on 1.10 vanilla minecraft
EDIT: they are 0 spawner custom or other, it's a pure vanilla survival
I'm not trying to criticize, but is "till" a proper word, or should it be changed to "until"?
Also, this bug is very annoying and I get it even in singleplayer. Does it only crash servers or singleplayer too?
And finally, what causes this?
Anybody able to reproduce in 1.10.1?
Yes i am able to reproduce running a 1.10.1 client and the error still persists. I get Item entity (numbers here) has no item?!, with the following numbers: 165757,159333,155797,155566,150825,129859 and 127536,
Example:
[04:49:07] [Client thread/ERROR]: Item entity 165757 has no item?!
[04:49:07] [Client thread/ERROR]: Item entity 165757 has no item?!
[04:49:07] [Client thread/ERROR]: Item entity 165757 has no item?!
Is that on a vanilla server? Anybody able to reproduce in 1.10.2 on a vanilla client & server?
Yes I'm seeing it on 1.10.2 while playing on a server.
If this is still happening why is this issue marked "Resolved"?
Because it was resolved as awaiting response, look at the resolution as well, instead of only the status.
@Jason Reed: On that server, please force a crash by holding F3+C for 10 seconds and attach the resulting crash report here.
Just reproduced in my vanilla singleplayer world.
Forced crash:
I'd like to comment that this happened to me too in Multiplayer. It seems to happen when spawning an item that doesn't exist (apparently).
I am using Spigot 1.10.2, which has a Material enum containing the 'COCOA' material. When spawning this item this error starts to pop up.
I'd also like to add that /give <me> cocoa results in "There is no such item with name minecraft:cocoa".
Sybren Gjaltema
Is this still an issue in the most recent versions (currently that is 1.13.2, or the latest snapshot 19w06a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.
This issue was technically fixed in 1.11 (=> 16w32a, the first snapshot); the message is no longer logged. However, the fix results in removing the items clientside (
MC-111978) which is a bit worse.I'm resolving this as fixed since technically it is fixed, in that there is no longer log spam or a stone item appearing.
I'm also going to clarify this issue to refer only to newly spawned items or invalid items displaying as stone or and spamming the log. (And as a very belated response to Sybren Gjaltema's comment: cocoa wasn't an item but only a block; it was only dye back then and spigot, being spigot, named dye ink sac. That's what your issue was, and it wouldn't apply in 1.13+.}}
Whatever crash was referenced is presumably separate and likely relates to old behavior with forcing invalid items to render; that crash report doesn't seem to exist anymore. There's also comments saying that the crash was modded only, so I think it's probably best to just completely exclude it. And this ticket was first created in a pre-1.8
era where you could use block IDs for all items, even invalid ones; that hasn't been a thing for a while.