Server crash on launch (setElementData, syncMode and clientChangesPolicy flags)

[gh0st2k2]

Describe the bug

I'm trying to host an server using Optiklink servers (Linux)
The server crashes instantly after resources start due to a segmentation fault.
After some research and investigations, I could isolate the resources causing this crash and one of them being this teams resource.

In the teams resource, there is some calls to setElementData on teams elements like this:

local team = createTeam(teamName, teamColor[1], teamColor[2], teamColor[3])
if not team then
    return false
end

setElementData(team, "NAME", teamName, true, "deny")
setElementData(team, "TAG", teamTag, true, "deny")
...

I tried and removed the setElementData code lines. The resource started and the server did not crash.
It also turned out that using syncMode and clientChangesPolicy flags cause this crash.
This works perfectly fine on a locally hosted server (Windows)

Steps to reproduce

call setElementData server-side when a resource starts with syncMode and clientChangesPolicy flags

Version

Server: MTA:SA Server v1.6-release-23069

Additional context

No response

Relevant log output

/entrypoint.sh: line 13:    15 Segmentation fault      (core dumped) ./mta-server64 --port ${SERVER_PORT} --httpport ${SERVER_PORT} --maxplayers ${MAX_PLAYERS} -n

MTA:SA Server v1.6-r23069-release crash report.
2025-08-04 13:53
Caught 32 addresses ...

Backtrace:
#0 - ./x64/core.so(+0x8c87e) [0x7f211e1c887e]
#1 - ./x64/core.so(+0xb50b5) [0x7f211e1f10b5]
#2 - ./x64/core.so(+0xb542f) [0x7f211e1f142f]
#3 - /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7f211e530420]
#4 - /home/container/x64/deathmatch.so(+0x22ecf1) [0x7f211c7f3cf1]
#5 - /home/container/x64/deathmatch.so(+0x2592f2) [0x7f211c81e2f2]
#6 - /home/container/x64/deathmatch.so(+0x3bc697) [0x7f211c981697]
#7 - /home/container/x64/deathmatch.so(+0x4c6e98) [0x7f211ca8be98]
#8 - /home/container/x64/deathmatch.so(+0x6254fd) [0x7f211cbea4fd]
#9 - /home/container/x64/deathmatch.so(+0x63af31) [0x7f211cbfff31]
#10 - /home/container/x64/deathmatch.so(+0x625b4d) [0x7f211cbeab4d]
#11 - /home/container/x64/deathmatch.so(+0x624e03) [0x7f211cbe9e03]
#12 - /home/container/x64/deathmatch.so(+0x625e20) [0x7f211cbeae20]
#13 - /home/container/x64/deathmatch.so(lua_pcall+0x59) [0x7f211cbe3919]
#14 - /home/container/x64/deathmatch.so(+0x42dd56) [0x7f211c9f2d56]
#15 - /home/container/x64/deathmatch.so(+0x41285e) [0x7f211c9d785e]
#16 - /home/container/x64/deathmatch.so(+0x2e26a0) [0x7f211c8a76a0]
#17 - /home/container/x64/deathmatch.so(+0x25cb0c) [0x7f211c821b0c]
#18 - /home/container/x64/deathmatch.so(+0x27bb5f) [0x7f211c840b5f]
#19 - /home/container/x64/deathmatch.so(+0x35842d) [0x7f211c91d42d]
#20 - /home/container/x64/deathmatch.so(+0x359327) [0x7f211c91e327]
#21 - /home/container/x64/deathmatch.so(+0x287a84) [0x7f211c84ca84]
#22 - /home/container/x64/deathmatch.so(+0x5f5820) [0x7f211cbba820]
#23 - /home/container/x64/deathmatch.so(+0x5f5be8) [0x7f211cbbabe8]
#24 - /home/container/x64/deathmatch.so(+0x277b6c) [0x7f211c83cb6c]
#25 - /home/container/x64/deathmatch.so(+0x1c2deb) [0x7f211c787deb]
#26 - ./x64/core.so(+0x90fd1) [0x7f211e1ccfd1]
#27 - ./x64/core.so(+0x92418) [0x7f211e1ce418]
#28 - ./x64/core.so(Run+0x6d) [0x7f211e1e646d]
#29 - ./mta-server64(main+0x26c) [0x558853de57dc]
#30 - /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f211e34e083]
#31 - ./mta-server64(_start+0x2e) [0x558853de5efe]
--------------------------------------------------------------------------------

Security Policy

• I have read and understood the Security Policy and this issue is not security related.