plankton@programming.dev to Selfhosted@lemmy.worldEnglish · edit-224 hours ago[OC] I haven't had time to look into it, ok?programming.devimagemessage-square21fedilinkarrow-up1324arrow-down113file-text
arrow-up1311arrow-down1image[OC] I haven't had time to look into it, ok?programming.devplankton@programming.dev to Selfhosted@lemmy.worldEnglish · edit-224 hours agomessage-square21fedilinkfile-text
minus-squareidunnololz@lemmy.worldlinkfedilinkEnglisharrow-up3·2 months agoTo “fix” the memory leak, just restart your server every day with a cron job /s
minus-squarezorro@lemmy.worldlinkfedilinkEnglisharrow-up2·2 months agoCron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.
minus-squarejonathan@piefed.sociallinkfedilinkEnglisharrow-up2·1 month agoMy actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅
![[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
Cron job too complicated, just buy one of those timed light controllers to power off the server every night for an hour.
My actual “solution” was to do nothing and just let Kubernetes restart it when it OOMs 😅