@plankton@programming.dev to Selfhosted@lemmy.worldEnglish • edit-21 month ago[OC] I haven't had time to look into it, ok?programming.devimagemessage-square21fedilinkarrow-up1321arrow-down113
arrow-up1308arrow-down1image[OC] I haven't had time to look into it, ok?programming.dev@plankton@programming.dev to Selfhosted@lemmy.worldEnglish • edit-21 month agomessage-square21fedilink
minus-squareidunnololzlinkfedilinkEnglish3•3 months agoTo “fix” the memory leak, just restart your server every day with a cron job /s
minus-squarejonathanlinkfedilinkEnglish2•3 months agoMy actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅
minus-square@zorro@lemmy.worldlinkfedilinkEnglish2•3 months agoCron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.
![[OC] I haven't had time to look into it, ok?](https://programming.dev/pictrs/image/17b169f0-9983-4629-982e-0d6dfafc626f.png){kind=link}
To “fix” the memory leak, just restart your server every day with a cron job /s
My actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅
Cron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.