stops sending data after about 4 minutes about h264-live-player HOT 2 CLOSED

I found the problem and solution at https://stackoverflow.com/questions/20792427/why-is-my-node-child-process-that-i-created-via-spawn-hanging.

Here's the copy of the solution:

As it turns out once the stderr buffer exceeds 24kb you must be reading from it or you not see any events for completion. Possible workarounds:

Set the stdio option on the spawn call.

spawn('git', ['push', 'origin', 'master'], {stdio: 'ignore'});
See Node ChildProcess doc for all of the possibilities - there are lots.
Add an on(data) handler.
var git = spawn('git', ['push', 'origin', 'master']);
...
git.stderr.on('data', function(data) {
// do something with it
});
Pipe it to stdout / stderr. This may be too verbose for your application but including it for completeness.
var git = spawn('git', ['push', 'origin', 'master']);
...
git.stderr.pipe(process.stderr);
git.stdout.pipe(process.stdout);

from h264-live-player.

If I put in _server.js -> new_client(socket) -> socket.on(...):

      if(action == "REQUESTSTREAM") {
        self.start_feed();
      }
	  
      if(action == "STOPSTREAM") {
		try {
			self.streamer.kill();
			self.readStream = undefined;
		} catch (er) {
			console.log("self.readStream ended");
		}
      }

where streamer is spawn('ffmpeg', args) from ffmpeg.js I obtain the killing of ffmpeg process when pressing Stop Video button; when pressing the Start Video button the ffmpeg process restarts (started by self.start_feed call) so everything works fine.

I tested this behavior with two very different cameras. So why from time to time (~ 4 minutes) the node's child_process (streamer from ffmpeg.js) stops getting data from ffmpeg process?

Again: with some other software the same time I'm getting data from the same camera.

from h264-live-player.