Laggy Behavior: No, not really. It happens pretty abruptly, usually signaled by anomalies such as duplicate (but, not real) connection listings in the UI suddenly appearing for all players.
SpeedTest: We run the server on AWS, so that's not an issue. Last test was 4500+MBPS both up and down. [Report]
Error Log: The last time it occurred, there were memory access violation entries and a couple of stack traces dumped to the log:
Code: Select all
2022-06-29 21:04:38|ProcessPacket error: Access violation at address 00000000007B268B in module 'PMService.exe'. Read of address FFFFFFFFFFFFFFFF, ID=00000138, Response=Login
2022-06-29 21:04:38|ProcessPacket error: Access violation at address 000000000093CF16 in module 'PMService.exe'. Read of address 0000000000000000, ID=00000131, Response=Login
2022-06-29 21:04:38|ProcessPacket error: Access violation at address 00000000007B268B in module 'PMService.exe'. Read of address FFFFFFFFFFFFFFFF, ID=0000013E, Response=Login
2022-06-29 21:04:38|ProcessPacket error: Access violation at address 00000000007B268B in module 'PMService.exe'. Read of address FFFFFFFFFFFFFFFF, ID=0000013D, Response=Login
2022-06-29 21:04:38|PlayerExecute error: Access violation at address 00000000007B268B in module 'PMService.exe'. Read of address FFFFFFFFFFFFFFFF
2022-06-29 21:04:38|ProcessPacket error: Access violation at address 00000000007B268B in module 'PMService.exe'. Read of address FFFFFFFFFFFFFFFF, ID=00000134, Response=Login
2022-06-29 21:04:38|PlayerExecute error: Access violation at address 000000000093CF16 in module 'PMService.exe'. Read of address 0000000000000000
2022-06-29 21:04:38|WSServerExecute error: Access violation at address 00000000007B268B in module 'PMService.exe'. Read of address FFFFFFFFFFFFFFFF
2022-06-29 21:04:38|WSServerExecute error: Access violation at address 000000000093CF16 in module 'PMService.exe'. Read of address 0000000000000000
2022-06-29 21:04:38|ProcessPacket error: Access violation at address 00000000007B268B in module 'PMService.exe'. Read of address FFFFFFFFFFFFFFFF, ID=00000127, Response=Login
2022-06-29 21:04:38|WSServerExecute stack trace 7.07: 007b268b PMService.exe IdContext 218 TIdContext.GetBinding - 0093cf0e PMService.exe Players 1854 TPlayerSession.ProcessLogin - 00952e87 PMService.exe Players 4134 TPlayerSession.ProcessPacket - 00934699 PMService.exe Players 632 PlayerSessionExecute - 00ac480d PMService.exe Main 1204 WSServerEvents.OnExecute - 007d6682 PMService.exe IdCustomTCPServer 553 TIdCustomTCPServer.DoExecute - 007b25b7 PMService.exe IdContext 185 TIdContext.Run - 007b04e7 PMService.exe IdTask 136 TIdTask.DoRun - 007d20b8 PMService.exe IdThread 697 TIdThreadWithTask.Run - 007d1347 PMService.exe IdThread 428 TIdThread.Execute - 004f97a4 PMService.exe madExcept HookedTThreadExecute - 005d5050 PMService.exe System.Classes 14561 ThreadProc - 0040eaf8 PMService.exe System 23354 ThreadWrapper - 004f9679 PMService.exe madExcept ThreadExceptFrame - 7ffa3e88 KERNEL32.DLL BaseThreadInitThunk - 7ffa3f16 ntdll.dll RtlUserThreadStart
2022-06-29 21:04:38|WSServerExecute stack trace 7.07: 0093cf16 PMService.exe Players 1854 TPlayerSession.ProcessLogin - 00952e87 PMService.exe Players 4134 TPlayerSession.ProcessPacket - 00934699 PMService.exe Players 632 PlayerSessionExecute - 00ac480d PMService.exe Main 1204 WSServerEvents.OnExecute - 007d6682 PMService.exe IdCustomTCPServer 553 TIdCustomTCPServer.DoExecute - 007b25b7 PMService.exe IdContext 185 TIdContext.Run - 007b04e7 PMService.exe IdTask 136 TIdTask.DoRun - 007d20b8 PMService.exe IdThread 697 TIdThreadWithTask.Run - 007d1347 PMService.exe IdThread 428 TIdThread.Execute - 004f97a4 PMService.exe madExcept HookedTThreadExecute - 005d5050 PMService.exe System.Classes 14561 ThreadProc - 0040eaf8 PMService.exe System 23354 ThreadWrapper - 004f9679 PMService.exe madExcept ThreadExceptFrame - 7ffa3e88 KERNEL32.DLL BaseThreadInitThunk - 7ffa3f16 ntdll.dll RtlUserThreadStart