FXServer crash in libnode22 / net-tcp-server.dll (INVALID_POINTER_READ c0000005) #3865
Description
What happened?
FXServer is crashing multiple times per day with an access violation in libnode22.dll, coming from net-tcp-server.dll.
The Windows minidump shows:
Process: FXServer.exe
Exception: 0xc0000005 (Access violation / INVALID_POINTER_READ)
Faulting module: libnode22.dll (libnode22!v8::CppHeap::wrapper_descriptor+0x1b5c)
Failure bucket: INVALID_POINTER_READ_c0000005_libnode22.dll!Unknown
Call stack tail (shortened):
libnode22.dll → libuv.dll → net-tcp-server.dll → ucrtbase!thread_start → kernel32!BaseThreadInitThunk → ntdll!RtlUserThreadStart
net_tcp_server.dll details:
Path: C:\Brasilandia\artifacts\net-tcp-server.dll
FileDescription: net-tcp-server for FXServer
FileVersion/ProductVersion: 1.0.0.26795
From the dump analysis, it looks like an invalid pointer read inside the embedded Node/V8 (libnode22) while handling TCP server activity (net-tcp-server.dll / libuv.dll).
No custom native DLLs are being loaded by my resources; the crash happens inside FXServer’s own binaries.
Expected result
FXServer should handle any invalid or unexpected TCP/network input gracefully without crashing the whole process. Even if a resource or external client misbehaves, the server process should not hit an INVALID_POINTER_READ inside libnode22 / net-tcp-server.dll.
Reproduction steps
Start FXServer with my usual configuration (Windows Server 2022, artifacts installed at C:\Brasilandia\artifacts).
Let the server run with normal player load (no custom native DLLs; only Lua/JS resources).
After some time (currently ~3 times per day), FXServer suddenly exits with a native crash.
Windows creates a full dump. Analyzing it in WinDbg with !analyze -v shows:
ExceptionCode: c0000005 (Access violation)
Failure.ProblemClass.Primary: INVALID_POINTER_READ
IMAGE_NAME: libnode22.dll (IMAGE_VERSION: 22.22.0.0)
PROCESS_NAME: FXServer.exe
Call stack with libnode22 → libuv → net_tcp_server.dll → ucrtbase!thread_start.
The crash is not tied to a specific in‑game action that I can reliably reproduce; it seems related to background TCP/server activity (panel, network services, etc.), but always ends in the same access violation inside libnode22.
I can provide one or more .dmp files if needed.
Importancy
Crash
Area(s)
FiveM
Specific version(s)
26803
Additional information
No response