Closed james-howard closed 6 years ago
I'm seeing this happen as well. Any updates planned to resolve this?
@gergderkson None immediately, but it's also not being ignored. While it's low impact and gets prioritized accordingly, it's at least on our radar.
@troy perfect thanks for the update!
This seems to be fixed in the latest release, so I am closing this issue. (Though to be honest, I couldn't find a leak in 0.9.17 either.)
If anyone is still seeing signs of a memory leak in the latest release, please email support@papertrailapp.com and we'll dig into the details.
Leaving
papertrail -f
running for a long period of time appears to accumulate memory proportionate to the amount of log messages seen.For instance, I had a couple of papertrail instances running this morning, and saw them each using over 300MB of RPRVT. Even tailing a fairly low traffic host for about an hour this afternoon I see ruby at ~95MB of RPRVT.