Prior to 1.18-Pre2 a user action which resulted in a stack overflow was handled gracefully by the server side of the game, either the embedded (single player) server or the standalone (multiplayer) server.

With the transition to Java 17 this is no longer the case and the exception

java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.util.PrivateSecurityManagerStackTraceUtil

is generated and the server stops.

Higher up in the stack trace there is a StackOverflow exception, but this appears to be swallowed up by this further exception while attempting to handle an exception.

This is reproduceable by having a line of powered rails bud powered and then updating on of the rails, this happens in a device known as an update suppressor, however this does occur in normal play as well when a large number of updates occur within the same action.