[1.20.1 forge] SIGSEGV Segfault while saving rift

[PikachuGabe]

Server segfaults during saving a rift. Mods are available here.
80fa77db-5e84-42fa-8bed-83839fbbe1fc.zip
Zip archive containing the rift that was causing a segfault, it may not be the same version the server was trying to save.
hs_err_pid676879.log
Log created by the segfault.

[PikachuGabe]

Could be caused by a conflict with dimthread if the mod is using thread unsafe methods, would also explain the lack of reports on the crash. I unfortunately cannot understand shit about the segfault's log, so I have no idea.

[gigaherz]

Ender-Rift is not designed to be thread-safe, it is littered with assumptions about when and how things happen. Specially because the mod allows ender-chest-like access to the contents of the rift from multiple structures, meaning multiple threads can easily access the contents of the rift concurrently, leading to race conditions.
I don't know how this would affect saving, though, since saving and loading happens exclusively from the overworld.
In any case, this should NOT cause a segfault, just data corruption. I wonder if the segfault is graal's issue. I would think it likely that it would just corrupt and not crash, if it was "vanilla" hotspot.

[PikachuGabe]

Interesting. I'll let the server owner know as I only have read access to the server.