Server memory error, now server log is looping!

[GoDodyGo]

I have already EXPRESS STOPPED the game but when I query the BGA request&SQL logs I can see the table is still running! How to stop it??

Here you can see the log updates every 10 seconds, even if I stop the game it continues:
https://studio.boardgamearena.com/1/tut ... 672#bottom

It gave some error (I lost it) that it tried to allocate some HUGE number of bytes but only got 16384. I think I inadvertently put in an endless loop between states. So, it's just sitting there looping around, even though I've quit the game...

What to do? I cannot launch another game because it thinks the previous one is the current one (strange). It's just looping between states.

I did one suggestion I found here to edit the database, but the Player_id was already OK, and the edit didn't stop the logging.

Thanks!

[GoDodyGo]

It seems I've spawned off some independent process that still outputs to the log. I've changed the code which creates the text "Waiting for buyer:", quit the game, quit all browsers, reloaded the PHP (CTRL+F5). I've started up a new game and I still see this text in the log every 10 seconds!

Code: Select all

... Other real logging above. The next text below is from a game with a bad state machine ~20 minutes ago and tried to kill...
31/10 03:25:15 [info] [T207572] [2333744/DodyOaks2] [bmc] ENTER NextPlayer3
31/10 03:25:15 [info] [T207572] [2333744/DodyOaks2] 0.078201293945312 SELECT player_id, buying FROM player 3
31/10 03:25:15 [info] [T207572] [2333744/DodyOaks2] [bmc] Waiting for buyer: = string(1) "0"3
3
31/10 03:25:15 [info] [T207572] [2333744/DodyOaks2] [bmc] Waiting for buyer: = string(1) "0"3
3
31/10 03:25:15 [info] [T207572] [2333744/DodyOaks2] [bmc] Waiting for buyer: = string(1) "0"3
3
31/10 03:25:15 [info] [T207572] [2333744/DodyOaks2] [bmc] Waiting for buyer: = string(1) "0"3
3
31/10 03:25:15 [info] [T207572] [2333744/DodyOaks2] [bmc] Still waiting, loop around (eventually)
...more real logging continues...

It is interspersed with my "real" logging info.

How to kill the underlying rogue process? Or will something eventually kill it?

[GoDodyGo]

Well somehow it stopped on its own. The rogue process ran for a bit more than 60 minutes, updating every 10 seconds in the log. Then it stopped on its own. Game was sitting there in a state idle. Strange, but I'm glad I didn't break anything (for much more than an hour)!