We just rolled out 3.13.5, I will update if we see additional issues with memory usage once we have some monitoring data with the new box.
Hi Matt,
Thanks for keeping in touch. Looking forward to hearing if you see the behaviour continue, or not.
We do have some work we are going to do soon to eliminate another source of over-allocation, which will help a lot with general memory pressure, but we still have no firm leads on a real “memory leak”.
Hope that helps!
Mike
I was just experiencing a very, very similar issue for the past few days.
It turns out there were Windows Updates waiting to be installed, and after I let those go forward with a reboot and everything we had normal memory usage back.
Very frustrating.
Hi!
Thanks for getting in touch. That’s interesting. So it didn’t turn out to be a problem with Octopus from what you can tell, but a problem caused by Windows Updates being queued?
I’d be interested to see if you experience a similar issue and can pinpoint it to Octopus.
Hope that helps!
Mike