Originally Posted by Padrinobta1
For future reference:
Those go to our 'Crash Logs' inbox that our QA/Testing Manager reviews. You can see the support tickets that were generated from the logs you sent on our support site. Here is a direct link to your My Tickets page. You could also click 'Don't Send' and then send us the logs manually so they arrive in one of our level 1 support ticket inboxes that we have more employee's monitoring.
The last set of logs you sent created ticket number 468351. That was a HUD 'APITimeout' issue for the HUD not updating for one hand, it wasn't a hard crash exception that would have closed HM3 on it's own. Did the HUD keep working after you sent those logs? Did the HM3 software completely shut down?
It appears, from the server log, that something other than HM3 on your system was using up all of your RAM:
Something slowed down your PC and/or it froze for 15 seconds. There was Tournament Detection and import of a single hand that took 15 seconds because of it which prevented the HUD from loading up fast enough.
2020/02/26 16:00:13.052  [HoldemManager.Server:PerformanceInfo:LogInfo(58)] [Info] [Server CPU: 16.06%, Mem: 1666.5Mb] [Total CPU: 55.6%, Mem: 13999.54Mb] [GC %: 0.07%]
Did you have the HM3 Hand History Viewer open often/constantly during this session? Were you on the Live Play view with the Auto Refresh option enabled the whole session, or switching between views and reports?
The next time you are playing and open your Windows Task Manager 'Memory' tab and sort the 'Memory' column in descending order of RAM use to see what is using your system resources. If the issue happens again take a screenshot of the Task Manager and your tables + HM3, then send us the screenshotsin a new support ticket and zip + attach your \Desktop\HM3logs\ folder files as instructed in this FAQ. with a detailed description of what you were doing during the session, what exactly happened, and what you were doing immediately before the issue happened.