You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java version:
Java 8:
OpenJDK 1.8.0_292 for Ubuntu on the server.
Java 1.8.0_301-b09 for Windows on the client.
Description: Erebus antlions cause a server crash when entering Erebus portals.
Later I tested spawning antlions and creepers and pushing them into the portal on seperate singleplayer worlds, and multiplayer servers. Antlions caused a crash, the creepers did not, although I am testing more extensively with other mobs from Erebus. I will update this with any further information.
Any mob of sufficient size can trigger this issue, including but not limited to:
Antlions, Rhinoceros beetles, Tarantula brood mothers, and the like.
I have received two distinct types of crash reports, examples of both types are linked to below.
When did the crash happen?
After exploring the Erebus dimension for some time, and attempting to return to the overworld, as well as any other attempts to move back and forth, until all hostile entities were killed.
Believed to be related to an antlion that wandered into the portal on the Erebus side, and then would travel through the portal in the opposite direction of the player when a player entered and loaded the area on the destination side of the portal.
The problem seemed to be resolved after "/cofh killall" was used in the server console to remove all hostile entities.
Join Server/Load World
Build Erebus portal.
Travel through at least once.
Spawn antlion using spawn egg.
Push into portal.
The server should crash.
On a multiplayer server, the server may be restarted and "/cofh killall" used in console to kill the antlion so that the affected player may rejoin without causing further crashes.
Note that using "/cofh killall" does not seem to always clear the antlion in question, and therefore is inconsistent.
This is pretty much a copy-paste from the Divine Journey 2 report at the link below, so be aware of that.
Divine-Journey-2/Divine-Journey-2#399
Erebus version:
1.0.32
Modpack version:
2.5.0
Java version:
Java 8:
OpenJDK 1.8.0_292 for Ubuntu on the server.
Java 1.8.0_301-b09 for Windows on the client.
Description:
Erebus antlions cause a server crash when entering Erebus portals.Later I tested spawning antlions and creepers and pushing them into the portal on seperate singleplayer worlds, and multiplayer servers. Antlions caused a crash, the creepers did not, although I am testing more extensively with other mobs from Erebus. I will update this with any further information.Any mob of sufficient size can trigger this issue, including but not limited to:
Antlions, Rhinoceros beetles, Tarantula brood mothers, and the like.
I have received two distinct types of crash reports, examples of both types are linked to below.
When did the crash happen?
After exploring the Erebus dimension for some time, and attempting to return to the overworld, as well as any other attempts to move back and forth, until all hostile entities were killed.
Believed to be related to an antlion that wandered into the portal on the Erebus side, and then would travel through the portal in the opposite direction of the player when a player entered and loaded the area on the destination side of the portal.
The problem seemed to be resolved after "/cofh killall" was used in the server console to remove all hostile entities.
Steps to reproduce:
A video example of me reproducing the crash can be found here:
http://qqlazors.com/mods/crash-reports/DJ2_antlion_portal_crash.mp4
Minecraft crash report:
All encountered crash reports can be found here:
Any future crash reports will also be added to this page
http://qqlazors.com/mods/crash-reports/crash-reports/
They mainly fall into two types, the:
"Description: Exception ticking world entities
java.lang.NoClassDefFoundError: net/minecraft/entity/Entity$2"
And the:
"Description: Colliding entity with block
java.lang.StackOverflowError"
Additional context:
The server was recently updated to 2.5.0, using an old world file.
Both the server and client have 32 GB of memory installed, and 8 GB allocated.
The text was updated successfully, but these errors were encountered: