Spawn too many ffmpeg process in background

[edwinharly]

It seems like every time it spawned a process for stream, the process didn't get killed, so the process are stacking so many in the background

[codealchemist]

I was able to reproduce.
Thanks for reporting this!

[codealchemist]

Hey @edwinharly, I just added a fix to kill ffmpeg when processing is done.
Also added new endpoints that should help avoid some scenarios where more instances where started (like directly hitting an audio URL from Chrome).

Still, there are cases where ffmpeg is going zombie:
Just tried with VLC, which doesn't request the whole file at once, but instead keeps the stream open and requests chunks at regular intervals. After killing VLC the ffmpeg process wasn't properly killed.
Will need to investigate this further.

Please, let me know if v2.3.0 is working better for you.
Thanks!

[edwinharly]

Glad to hear it, I'll test it if I've got the chance to and let you know after that

[DavidBerdik]

Out of curiosity, how does the server handle livestreams? If I start streaming one, and then close it, will the ffmpeg instance supporting it be killed too, or will it continue running?