Page 1 of 1

Last Version 7.33 Integer Overflow - Starting Problems

Posted: Sun Jul 12, 2026 6:04 pm
by APC
Hi,
with the newest update I got problems to start my server.
After the normal update procedure, I get the following if I try to start the Server via the Web-GUI.
(Service Registration is working, and after a complete Windows Server reboot it´s starting, but still in the Web-GUI not possible to Stop/Start)

Start:
Image

Stop:
Error Stopping server. See Error Log.
Logs:

Code: Select all


2026-07-13 00:28:14|Stop Server error: Access violation at address 005368F8 in module '
PMService.exe'. Read of address 0000003C
2026-07-13 00:28:14|StopServer stack trace 7.33: 005368f8 
PMService.exe System.Classes 15415 TThread.Terminate - 008be603 
PMService.exe Main            1684 StopServer - 008c08e0 
PMService.exe Main            2202 Shutdown - 008c0d63 
PMService.exe MainService       54 TPokerMavens7.ServiceStop - 006383a9 
PMService.exe Vcl.SvcMgr       782 TService.DoStop - 00637a70 
PMService.exe Vcl.SvcMgr       431 TServiceThread.ProcessRequests - 0063785d 
PMService.exe Vcl.SvcMgr       392 TServiceThread.Execute - 004a57b7 
PMService.exe madExcept            HookedTThreadExecute - 00535965 
PMService.exe System.Classes 14561 ThreadProc - 00409dac 
PMService.exe System         23406 ThreadWrapper - 004a569d 
PMService.exe madExcept            CallThreadProcSafe - 004a5702 
PMService.exe madExcept            ThreadExceptFrame - 74e105c7 KERNEL32.DLL                       BaseThreadInitThunk
2026-07-13 00:30:02|Stop Server error: Access violation at address 005368F8 in module '
PMService.exe'. Read of address 0000003C
2026-07-13 00:30:03|StopServer stack trace 7.33: 005368f8 
PMService.exe System.Classes 15415 TThread.Terminate - 008be603 
PMService.exe Main            1684 StopServer - 008c08e0 
PMService.exe Main            2202 Shutdown - 008c0ca0 
PMService.exe MainService       41 TPokerMavens7.ServiceShutdown - 00638499 
PMService.exe Vcl.SvcMgr       816 TService.DoShutdown - 00637a94 
PMService.exe Vcl.SvcMgr       434 TServiceThread.ProcessRequests - 0063785d 
PMService.exe Vcl.SvcMgr       392 TServiceThread.Execute - 004a57b7 
PMService.exe madExcept            HookedTThreadExecute - 00535965 
PMService.exe System.Classes 14561 ThreadProc - 00409dac 
PMService.exe System         23406 ThreadWrapper - 004a569d 
PMService.exe madExcept            CallThreadProcSafe - 004a5702 
PMService.exe madExcept            ThreadExceptFrame - 74e105c7 KERNEL32.DLL                       BaseThreadInitThunk
2026-07-13 00:34:17|Error starting game server: Could not bind socket.
2026-07-13 00:35:55|Stop Server error: Access violation at address 005368F8 in module '
PMService.exe'. Read of address 0000003C
2026-07-13 00:35:55|StopServer stack trace 7.33: 005368f8 
PMService.exe System.Classes    15415 TThread.Terminate - 008be603 
PMService.exe Main               1684 StopServer - 007ed5f2 
PMService.exe Admin              6332 TAdminSession.ServerStop - 007f9058 
PMService.exe Admin              8480 TAdminSession.ProcessPacket - 007cc69e 
PMService.exe Admin               427 AdminSessionExecute - 008bd71d 
PMService.exe Main               1327 WSServerEvents.OnExecute - 0068a842 
PMService.exe IdCustomTCPServer   553 TIdCustomTCPServer.DoExecute - 0066d4a5 
PMService.exe IdContext           185 TIdContext.Run - 0066bf12 
PMService.exe IdTask              136 TIdTask.DoRun - 00688615 
PMService.exe IdThread            751 TIdThreadWithTask.Run - 00687d77 
PMService.exe IdThread            436 TIdThread.Execute - 004a57b7 
PMService.exe madExcept               HookedTThreadExecute - 00535965 
PMService.exe System.Classes    14561 ThreadProc - 00409dac 
PMService.exe System            23406 ThreadWrapper - 004a569d 
PMService.exe madExcept               CallThreadProcSafe - 004a5702 
PMService.exe madExcept               ThreadExceptFrame - 747005c7 KERNEL32.DLL                          BaseThreadInitThunk

It's working at the moment if no one touch it, but did not find a root cause.
Server is up to date, never so far faced this problem.
Was trying to run update again and restarted - no luck.

Thanks for checking - I hope I missed nothing.

Best
APC

Re: Last Version 7.33 Integer Overflow - Starting Problems

Posted: Sun Jul 12, 2026 6:55 pm
by Kent Briggs
You mentioned getting an error starting the server but the stack dump you showed indicated an error stopping the server. What action did you perform when you got that "Integer overflow" popup? Was it clicking the Start button? Because the stack dump appears to show a different error that was trigged by clicking the Stop Service button in the PM Service Manager.

Which version of Windows are you running?

Re: Last Version 7.33 Integer Overflow - Starting Problems

Posted: Mon Jul 13, 2026 3:31 am
by APC
Hi Kent,

the "Integer" Overflow comes when I hit "Start" in the Web-GUI.
And here it´s only in the Logs:

Code: Select all

2026-07-13 00:34:17|Error starting game server: Could not bind socket.
For sure I have tried to start/stop it - like a reboot always help, but also the "Stop" is not working and bring also errors.

Server:
Microsoft Windows Server 2019
Version 1809 (05 Build 17763.8880)

I see currently also that the complete Service is (in the Poker Maven Service Manager 7.33) not started after a reboot, but it´s working - what means Service is "running, but not started", the Web-GUI is also offline and I can not "Start/Stop" via GUI. Login to the Application Server as a Player is working...

My guess is that the Service is starting when the Server comes up, but the "Poker Maven Service Manager" can not start or handle it, because it´s already started. I have (as always) before I run the update done the "Unregister Service" - but looks looks this time with the newest version the Service is not in an healthy status.

Best
APC

Re: Last Version 7.33 Integer Overflow - Starting Problems

Posted: Mon Jul 13, 2026 12:54 pm
by Kent Briggs
I just sent you an email with a link to a beta version I would like for you to try. It should trap that error and give me a better idea of what is causing it.

Re: Last Version 7.33 Integer Overflow - Starting Problems

Posted: Mon Jul 13, 2026 3:23 pm
by Kent Briggs
Just to close this out, the stack trace pointed to the startup code that was preparing to delete old lobby chat files base on a user setting, which is not currently range checked. So if you put a large value like 10000000 (1 million days) then that will trigger an integer overflow or divide by zero error code exception and crash the site. The correct value to disable file deletion is just 0 but I will put a range check on those type of settings in the next update.

Re: Last Version 7.33 Integer Overflow - Starting Problems

Posted: Mon Jul 13, 2026 4:21 pm
by APC
Hi Kent,
exactly what you say was solving the problem and the server could be started normally.

My setting for "Maximum lobby chat days" was set to 999.999.

Thanks for the fast and great support + effort you took into it to build a extra version for this :!:

Best
APC

Re: Last Version 7.33 Integer Overflow - Starting Problems

Posted: Mon Jul 13, 2026 6:21 pm
by Kent Briggs
What was happening is that the code was building a date in the past so it would know anything older should be deleted. My Delphi compiler has a DateTime function that supports dates back to 100 AD. The problem is that 1 million days ago is somewhere around 700 BC. There are 5 other settings with the same problem. They actually have range checks on them but they are all set to 1 million max, which will also crash. Apparently I never tested those. I will lower all those to 100k in the next update.