You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prior to... seemingly literally today, this bot was running for literal months without issue. All of a sudden it starts triggering kernel's OOM kill switch and I can't get it running again. I have not updated anything in the code since I initially started running it months ago. After this point the kernel just kills it.
Ah, didn't realise there was a new version... updated it and checked again, I'm not getting the messages about the channel type anymore.... still getting memory leaks though. Not sure what to make of it. The code that was perfectly fine for months now is suddenly causing memory leaks :(
FWIW I'm still getting out of memory crashes seemingly when registering slash commands, regardless of whether the guild(s) it's connected to have forum channels or not. :/
I'm running this on Ubuntu, on a DigitalOcean droplet if that matters.
Log up until kernel kill from OOM
Prior to... seemingly literally today, this bot was running for literal months without issue. All of a sudden it starts triggering kernel's OOM kill switch and I can't get it running again. I have not updated anything in the code since I initially started running it months ago. After this point the kernel just kills it.
Code I'm currently running is viewable here:
https://github.com/vexx32/thread-tracker/tree/badf900f76d60c7d043890e873015cac228eb4d7
I have a newer version of the code using slash-commands which is exhibiting the same issue:
https://github.com/vexx32/thread-tracker/tree/shuttle-less
The text was updated successfully, but these errors were encountered: