Can confirm in 1.20.1. Also, this has nothing to do with spawn protection and occurs in the entire world.
Can confirm in 23w12a
Can confirm in 1.19.4
The server now throws an IllegalStateException before the NullPointerException
[17:54:28] [Server thread/WARN]: **** FAILED TO BIND TO PORT!
[17:54:28] [Server thread/WARN]: The exception was: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use
[17:54:28] [Server thread/WARN]: Perhaps a server is already running on that port?
[17:54:28] [Server thread/ERROR]: Encountered an unexpected exception
java.lang.IllegalStateException: Failed to initialize server
at net.minecraft.server.MinecraftServer.runServer(SourceFile:688) ~[server-1.19.4.jar:?]
at net.minecraft.server.MinecraftServer.lambda$spin$2(SourceFile:266) ~[server-1.19.4.jar:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
[17:54:28] [Server thread/ERROR]: This crash report has been saved to: /home/finn/vanilla/./crash-reports/crash-2023-03-20_17.54.28-server.txt
[17:54:28] [Server thread/INFO]: Stopping server
[17:54:28] [Server thread/INFO]: Saving worlds
[17:54:28] [Server thread/ERROR]: Exception stopping the server
java.lang.NullPointerException: Cannot invoke "net.minecraft.server.level.ServerLevel.getWorldBorder()" because "$$5" is null
at net.minecraft.server.MinecraftServer.saveAllChunks(SourceFile:545) ~[server-1.19.4.jar:?]
at net.minecraft.server.MinecraftServer.stopServer(SourceFile:606) ~[server-1.19.4.jar:?]
at net.minecraft.server.dedicated.DedicatedServer.stopServer(SourceFile:536) ~[server-1.19.4.jar:?]
at net.minecraft.server.MinecraftServer.runServer(SourceFile:707) ~[server-1.19.4.jar:?]
at net.minecraft.server.MinecraftServer.lambda$spin$2(SourceFile:266) ~[server-1.19.4.jar:?]
at java.lang.Thread.run(Thread.java:833) ~[?:?]
It starts with 35792. 35791 and below work fine.
They just need to update lwjgl to version 3.3.1 and the Java-Objective-C-bridge to version 1.1 and then it would run completely native on M1.
No, this is a completely different bug and has no connection with the bug report you linked.
Good to know, but where can I report this kind of mapping problem so that it gets fixed and is not flagged as invalid?
Also, can still confirm in 1.20.2-pre2.