FFMPEG not terminateing when using QSV

[Tranquil 94]

Hello Luke and Devs.

 

In general, QSV is working fine on my machine, saving me ~70% of CPU power while transcoding for a Amazon TV stick. Unfortunately, there is one problem, which I assume should be fixable:

 

The server does not kill ffmpeg instances when they are not being used any longer for example when jumping inside a stream or starting other streams. Sometime it works, but often it does not. For me, this is easy to reproduce, so if you need a log, just let me know.

 

It would be so nice to see this fixed as for now, the QSV method is unusable. Yesterday I had 5 ffmpeg instances running consuming all my CPUs power and no playback was active.

[MSattler 390]

Hello Luke and Devs.

 

In general, QSV is working fine on my machine, saving me ~70% of CPU power while transcoding for a Amazon TV stick. Unfortunately, there is one problem, which I assume should be fixable:

 

The server does not kill ffmpeg instances when they are not being used any longer for example when jumping inside a stream or starting other streams. Sometime it works, but often it does not. For me, this is easy to reproduce, so if you need a log, just let me know.

 

It would be so nice to see this fixed as for now, the QSV method is unusable. Yesterday I had 5 ffmpeg instances running consuming all my CPUs power and no playback was active.

 

Typically I see this most with Live TV, where sometimes playback fails but the ffmpeg process keeps running.  With movies and tv shows I rarely see this.

[ZachOfAllTrades 0]

I have had emby hang multiple times and I think this may be related -- the last error in the log is a System.Net.Sockets.SocketException with the description message "Too many open files". I had another window open monitoring running processes, and emby clearly keeps spawning child processes that never get terminated.