plankton@programming.dev to Selfhosted@lemmy.worldEnglish · edit-22 days ago[OC] I haven't had time to look into it, ok?programming.devimagemessage-square9linkfedilinkarrow-up12arrow-down10file-text
arrow-up12arrow-down1image[OC] I haven't had time to look into it, ok?programming.devplankton@programming.dev to Selfhosted@lemmy.worldEnglish · edit-22 days agomessage-square9linkfedilinkfile-text
minus-squarejonathan@piefed.sociallinkfedilinkEnglisharrow-up1·2 months agoMy latest example of this was a memory leak in some old software I wrote. It grew linearly with traffic, so it wasn’t until traffic randomly spiked that I started seeing problems.
minus-squareidunnololz@lemmy.worldlinkfedilinkEnglisharrow-up1·2 months agoTo “fix” the memory leak, just restart your server every day with a cron job /s
minus-squarejonathan@piefed.sociallinkfedilinkEnglisharrow-up1·2 months 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}
My latest example of this was a memory leak in some old software I wrote. It grew linearly with traffic, so it wasn’t until traffic randomly spiked that I started seeing problems.
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 😅