[Windows] Syside server repeatedly crashes with access violation (0xC0000005); auto-restart stops after 5 attempts

Summary
On 2025-11-05 17:02:46 (KST, UTC+9), the Syside server hit an unhandled exception 0xC0000005 (access violation) and exited with code 1. The supervisor then reported that the server crashed 5 times within ~3 minutes and disabled further restarts.

Environment

  • OS: Windows (64-bit, system locale: Korean)

  • Product: Syside server (exact version/build unknown—latest installed as of Nov 5, 2025)

  • Repro frequency: Always (5/5 restarts failed within minutes)

Steps to Reproduce

  1. Start the Syside server normally.

  2. Observe that it runs briefly and then crashes.

  3. After several rapid crash cycles, the supervisor stops attempting restarts.

Expected Result
Server process stays up without crashing.

Actual Result
Server terminates with an unhandled exception 0xC0000005. After 5 crashes in ~3 minutes, the supervisor stops restarting it.

Impact/Severity
High — service becomes unavailable and does not auto-recover.

Notes

  • The log line contains mojibake from the Korean message, which should roughly read: “An attempt was made to access an invalid memory location.”

  • The stack includes UnhandledExceptionFilter, strncpy, and _C_specific_handler, followed by several frames within the Syside binary region (0x0000000140…), and finally wcsrchrBaseThreadInitThunkRtlUserThreadStart. This may hint at a string/buffer operation prior to the fault (not confirmed).

2025-11-05 17:02:46.497 [error] Thread 23952: An unhandled exception 0xc0000005: �߸��� �޸� ��ġ�� �׼����Ϸ��� �߽��ϴ�.
2025-11-05 17:02:46.497 [error]
2025-11-05 17:02:46.497 [error]
2025-11-05 17:02:46.497 [error]
2025-11-05 17:02:46.498 [error] Stack trace (most recent call first):
2025-11-05 17:02:46.498 [error] #0  0x0000000140618d86 in  ??
2025-11-05 17:02:46.498 [error] #1  0x0000000140626679 in  ??
2025-11-05 17:02:46.498 [error] #2  0x0000000180116082 in UnhandledExceptionFilter
2025-11-05 17:02:46.498 [error] #3  0x000000018016a6e2 in strncpy
2025-11-05 17:02:46.498 [error] #4  0x00000001801219b2 in _C_specific_handler
2025-11-05 17:02:46.498 [error] #5  0x00000001801663fe in _chkstk
2025-11-05 17:02:46.498 [error] #6  0x0000000180012326 in RtlLocateExtendedFeature
2025-11-05 17:02:46.498 [error] #7  0x0000000180165d3d in KiUserExceptionDispatcher
2025-11-05 17:02:46.498 [error] #8  0x00000001404d48bd in  ??
2025-11-05 17:02:46.498 [error] #9  0x00000001404d474a in  ??
2025-11-05 17:02:46.498 [error] #10 0x000000014040e6cf in  ??
2025-11-05 17:02:46.498 [error] #11 0x000000014040e516 in  ??
2025-11-05 17:02:46.498 [error] #12 0x000000014040e273 in  ??
2025-11-05 17:02:46.498 [error] #13 0x000000014040de5f in  ??
2025-11-05 17:02:46.498 [error] #14 0x00000001400b6b5a in  ??
2025-11-05 17:02:46.498 [error] #15 0x00000001400b5bc1 in  ??
2025-11-05 17:02:46.498 [error] #16 0x000000014045bb0e in  ??
2025-11-05 17:02:46.498 [error] #17 0x000000014045b97a in  ??
2025-11-05 17:02:46.498 [error] #18 0x00000001800037af in wcsrchr
2025-11-05 17:02:46.498 [error] #19 0x000000018002e8d6 in BaseThreadInitThunk
2025-11-05 17:02:46.498 [error] #20 0x000000018008c53b in RtlUserThreadStart
2025-11-05 17:02:46.501 [error] Server process exited with code 1.
2025-11-05 17:02:46.502 [error] The Syside server crashed 5 times in the last 3 minutes. The server will not be restarted.
See the output for more information.

Requested Assistance

  • Please advise on how to collect a symbolized stack or crash dump if needed. I can provide additional logs, config files, and full dumps on request.

  • If there’s a known fix or a build with extra diagnostics for this code path, I’m happy to test it.

Thanks for the report, I will have a look.

Please advise on how to collect a symbolized stack

Not needed, we can symbolize the stack trace internally from the addresses.

0xC0000005 is typically null-pointer access exception. In the given trace there should never be a null-pointer in the first place. Can you set "syside.logLevel": "trace" in VS Code settings and upload the log file?