Massive memory footprint from rtmpdump

[Peter S Kirk]

On 10 Feb 2014 at 20:19, dinkypumpkin dinkypumpkin <dinkypumpkin at gmail.com> 
wrote:

> On 10/02/2014 17:39, Nick wrote:
> > On Mon, 10 Feb 2014 15:20:12 +0000
> > Jimmy Aitken <jimmy.aitken at gmail.com> wrote:
> >> Does anyone have any thought as to why this may have started?  I'm now
> >> reticent to leave any jobs running automatically via cron in case this
> >> starts up again, and my machine in unusable when I get back to it.
> 
> This problem has been reported a number of times over the years. 
> Apparently, when rtmpdump is fed garbage or suffers dropouts due to 
> upstream problems, it can sometimes become a runaway and begin eating 
> memory.  Perhaps it's just obeying some bogus parameter values - I don't 
> really know.  There was a patch to rtmpdump a couple of years ago 
> purporting to address the problem, but it hasn't proved to be a complete 
> solution.  I've been hit a few times, but like you I've never been able 
> to repeat the error to debug it.

Possibly related to above gigo runaway. Occasionaly rtmpdump is downloading 
at ~500KBS, but no files are increasing in size.