Sorry for the vagueness of the question, but if anyone has any clues off the top of their head, please comment.

I've got a game running on a PC in an arcade cabinet at a local bar that I visit weekly. Usually, by the end of the week, the game is stuttering a little, and most importantly, if I try and Ctrl/alt/delete to see what's up with resources, or try and use the computer at the same time the game is running, the mouse arrow also stutters greatly- as if the computer is just totally overloaded, or trying to do something it can't (but the numbers in the task manager don't reflect that). -The computer is just in the cab, running that one game, not doing anything else besides it's own processes.

Anyways, my question is: what's your opinion on this?

1. It could just be a problem with the game of course, but it's numbers look great in the debug- I can't find anything that's building up or continuing to use resources. --But I can't run it in debug mode at the bar, so I haven't seen what it looks like exactly after a week of plays. but it runs great-- till it's been a whole week. If there's some memory management practices to share, please do.

2. It's exported to NW.js format, is it possible the windows 10 has a problem keeping that window open and running smooth? If so, is it possible that the windows webview2 would be any different?

3. I've experimented with trying to turn off anti-malware executable, and checking power settings to try and make sure it's prioritizing the game, but I haven't nailed down what the problem could be.

4. I am a novice in general, so could be missing something easy, please LMK if you've got a theory or some knowledge about these ideas. Or if you've got any hints that would relate to keeping a game running stable indefinitely. --In the game's form (arcade machine), it's intended to remain on indefinitely- is there anything inherent to NW.js or WebView2 or even construct 3 that would interfere with that at all?

Or if it's the game, can anyone think of commands/strategies for cleaning the slate during it's run, or any ideas on how I could get it to reset itself once a day?

My intuition tells me a a problem with the game, but it appears to be running so cleanly, that I thought to ask about these other things to (the computer, program format, relationship between computer/NW.js, etc.)

Thanks so much if you've got ideas