spectrum:invisible_item_frame
aolsen96 opened this issue ยท 18 comments
an entity with the id spectrum:invisible_item_frame seem to be caousing some problems,
first noticed this playing on a server(in that the server crashed) but can replicate siminlar behiver in sigle player
it does not crash in single player but it does hower take some time to open a chest at times when flying around in the ocean.
server crashes dou to a game tick taking to long.
eslily enough reproduced by flying around the ocean opening chests.
pack version 1.9.1
its not causing problems. thats correlation. the crash is likely from outdated structures being generated and taking too long to run the datafixerupper. You should also see in the console the structure's mod so that you can report the issue to the mod dev to get it resolved.
If you want to avoid the issue entirely, you have 2 options:
- pregenerate your world.
- run all the outdated structures through an update tool like https://github.com/jaskarth/structure-fixer (would require exporting the structures, updating them, then adding them back as a datapack. can put that datapack in the paxi folder or put the files in the kubejs/data folder)
If you choose to pregenerate your world, set max-tick-time to -1 during the pregeneration
If you mean the server log event "Hanging entity at invalid position" that is just https://bugs.mojang.com/browse/MC-252934 - purely visual and not the reason for the crash.
I think they are referring to this bug, I was able to find other examples of it dating back to May, and currently happening on my server as well. Correlation is an interesting way to put it, when console spams the entity frames immediately before a crash.
[23:24:10] [Server thread/INFO]: MapleASL is now AFK. [23:26:41] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:26:41] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:27:05] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:27:05] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:27:59] [Worker-Main-19/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:27:59] [Worker-Main-19/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:29:14] [Worker-Main-26/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:29:14] [Worker-Main-26/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:30:48] [Worker-Main-19/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:30:48] [Worker-Main-19/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:30:50] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:30:50] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:31:55] [Server thread/WARN]: UUID of added entity already exists: class_1540['Falling Block'/179983, l='ServerLevel[AOF6]', x=10404.50, y=76.00, z=-7983.50] [23:32:43] [Server thread/WARN]: UUID of added entity already exists: class_1540['Falling Block'/181030, l='ServerLevel[AOF6]', x=10430.50, y=77.00, z=-8010.50] [23:32:57] [Worker-Main-26/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:32:57] [Worker-Main-26/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:33:06] [Server thread/WARN]: UUID of added entity already exists: class_1540['Falling Block'/181717, l='ServerLevel[AOF6]', x=10430.50, y=77.00, z=-8008.50] [23:33:41] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame [23:33:41] [Worker-Main-122/WARN]: Skipping Entity with id spectrum:invisible_item_frame
Cuts off abruptly at the crash, unfortunately
it appears you are flying around and the world is struggling to handle it, and eventually you crash. there are known memory leaks in world generation and world generation takes quite a lot of processing power. the "spamming" being seen isnt really spamming, you can see the timestamps are different, it just happens that the world is generating several as you move through the world.
The crashlog from the crash-reports folder would show the underlying issues, or if you are on a host that kills servers when they exceed memory (shockbyte for instance), you wouldnt even get a crashlog as they just stop the entire process forcefully.
notice the frequent Ignoring block break at class_2338{x=333, y=77, z=-7253} because it was previously broken messages that also indicate your server is struggling to keep up
are you forceloading chunks?
Actively no? Before the server was started we pregen'd 5000x5000; but we're within that radius currently
Unfortunately, though, this isnt the case; The three of us that are online are currently working on a creative build almost 3000 blocks away from this
if you are not forceloading, then the server should not be processing something 3k blocks away. that would equate to roughly a 180 chunk radius.... Are you opening loot chests that might be generating maps? do you have the crashlog from the crash-reports folder?
if you are not forceloading, then the server should not be processing something 3k blocks away. that would equate to roughly a 180 chunk radius.... Are you opening loot chests that might be generating maps? do you have the crashlog from the crash-reports folder?
Where would I find the crash-reports folder? ^^;
All I see related is logs.
looks like it did not crash. you would have a crash-reports folder next to all those other folders, and inside that you would have the crashlog
:| And yet it has, multiple times. Interesting.
looks like it did not crash. you would have a crash-reports folder next to all those other folders, and inside that you would have the crashlog
It sounds like maybe your host is killing your session due to resource utilization. i would reach out to whoever you are hosting with to verify.
Hmmmm... not having a carsh report means the server might indeed have been killed by the OS / hoster, or hung in a way that the servers own hang detection did not recognise it.
ounds like maybe your host is killing your session due to resource utilization. i would reach out to whoever you are hosting with to verify.
I'll definitely reach out to CloudNord and see if this is an issue, though I cannot imagine where it would be; the server is on a high end plan, and I havent witnessed anything peaking in usage outside of the pregen early on
Even a jvm crash generates a crashlog. What you are seeing looks exactly like the host is killing it. If you have a way of watching the console, that might give insight as well. A console won't just stop either.
