eliteSCHW31N

uhm sure. its not a elegant test method but it works ``` sudo systemctl stop MoonCord sudo apt install screen screen -S mooncordTest cd ~/home/mooncord /usr/bin/npm run debugstart /home/pi/printer_data/config/ ```...

hmm. thats actuelly a good point. well i guess now that i didnt fix the memory leaks. i will take a look and try to fix it.

 i added the inspect mode to debug start, this gives even more details via inspector mode from chrome (they use both the same engine)

 on the first looks, it looks like that discordjs has a memory leak. i will wait a little bit longer

interesting. its also "old space". the profiler triggers garbage collect before making a snapshot. so its just garbage somewhere?

 it seems like that the latest patches fixed it? testing it with a profile currently for some hours and hopefully i can backtrace the source of the memory leak.

the latest on the main branch

hey there, i will look after this after work

is this resolved?

i didnt even started yet