Crashes on BeamMP Server v3.8.1

[spiikki]

Trying to install mod, but server crashes with segmentation fault. Most likely bug/error on lua side.

Here is valgrind dump from crash

==99236== Memcheck, a memory error detector
==99236== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==99236== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==99236== Command: ./BeamMP-Server.ubuntu.22.04.x86_64
==99236==
[03/02/25 08:26:05] [INFO] Server name set in new impl: BeamMP Server
[03/02/25 08:26:05] [INFO] BeamMP Server v3.8.1
[03/02/25 08:26:05] [INFO] Lua v5.3.6
[03/02/25 08:26:06] [INFO] Loaded 2 Mods

==99236== Thread 5:
==99236== Use of uninitialised value of size 8
==99236== at 0x2E0881: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x223165: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x223357: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x2ADCAB: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x4872AD5: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x487CF83: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x4872FC7: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x486B746: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x486DFDA: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x4872E9D: lua_pcallk (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x31DF25: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x2A0CB0: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236==
==99236== Invalid read of size 8
==99236== at 0x2E0881: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x223165: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x223357: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x2ADCAB: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x4872AD5: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x487CF83: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x4872FC7: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x486B746: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x486DFDA: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x4872E9D: lua_pcallk (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x31DF25: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x2A0CB0: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==99236==
==99236==
==99236== Process terminating with default action of signal 11 (SIGSEGV)
==99236== Access not within mapped region at address 0x0
==99236== at 0x2E0881: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x223165: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x223357: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x2ADCAB: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x4872AD5: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x487CF83: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x4872FC7: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x486B746: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x486DFDA: ??? (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x4872E9D: lua_pcallk (in /usr/lib/x86_64-linux-gnu/liblua5.3.so.0.0.0)
==99236== by 0x31DF25: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== by 0x2A0CB0: ??? (in /home/beamserver/beammp/BeamMP-Server.ubuntu.22.04.x86_64)
==99236== If you believe this happened as a result of a stack
==99236== overflow in your program's main thread (unlikely but
==99236== possible), you can try to increase the size of the
==99236== main thread stack using the --main-stacksize= flag.
==99236== The main thread stack size used in this run was 8388608.
==99236==
==99236== HEAP SUMMARY:
==99236== in use at exit: 387,501 bytes in 4,726 blocks
==99236== total heap usage: 39,307 allocs, 34,581 frees, 1,442,194 bytes allocated
==99236==
==99236== LEAK SUMMARY:
==99236== definitely lost: 0 bytes in 0 blocks
==99236== indirectly lost: 0 bytes in 0 blocks
==99236== possibly lost: 8,453 bytes in 16 blocks
==99236== still reachable: 379,048 bytes in 4,710 blocks
==99236== suppressed: 0 bytes in 0 blocks
==99236== Rerun with --leak-check=full to see details of leaked memory
==99236==
==99236== Use --track-origins=yes to see where uninitialised values come from
==99236== For lists of detected and suppressed errors, rerun with: -s
==99236== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)