Emby FFMPEG Open many times in task manager.

[zyfinity 15]

Hi, i have checked my task manager and occasionally around 5 ffmpeg tasks open up and completely slow down my system, and even after looking at the logs i cant seem to figure out what's causing it. and yes i did try disabling the screengraber option for all libraries. Is there something simple that im missing here? as its happened around 10 times this week and seems like a simple bug.

[Luke 42085]

Hi there, let's look at an example. Please attach the information requested in how to report a problem. Thanks !

[zyfinity 15]

ok, ill wait for it to happen again and will send the logs.

[zyfinity 15]

Hi, here is both the emby server and ffmpeg logs, NOTE i noticed about 5 ffmpeg processes in task manager pegging my i7 3770 to 100% cpu usage and nobody was transcoding, i also noticed these tasks open for about 6 hours until i force closed them in task manager. Please fix this bug as it makes actual transcoding slower since my cpu is already pegged at 100%

 

 

embyserver.txt

ffmpeg-transcode-3bfb338b-e6c5-4b60-af04-116552c2c543_1.txt

[zyfinity 15]

I just had this issue again today, to add i think this issue spawns from another bug in the emby server where sometimes when play is clicked it just loads forever and transcoding/ playing never starts, the user then goes back and clicks on it and it seems the work fine, the problem is that now there are two FFMPEG tasks in the task manager and both seem to be using alot of CPU and seem to be doing something, this is a really huge bug so a fix is really needed, the logs are provided above.

[Luke 42085]

I just had this issue again today, to add i think this issue spawns from another bug in the emby server where sometimes when play is clicked it just loads forever and transcoding/ playing never starts, the user then goes back and clicks on it and it seems the work fine, the problem is that now there are two FFMPEG tasks in the task manager and both seem to be using alot of CPU and seem to be doing something, this is a really huge bug so a fix is really needed, the logs are provided above.

 

I think it is loading, but in the log you provided above the transcoding is not fast enough to be playable. So it looks to me like it's just loading slowly.

[zyfinity 15]

It's definitely fast enough since after refreshing and clicking play it seems to run perfectly fine, it also seems to be getting around 150 FPS so I don't think speed is the issue.

[theghost31 4]

I agree with @@zyfinity, hoping we talk about the same issue . Its seems to be close.

I already saw this issue.

I got this issue since 6 months, maybe more.

It's only when emby had some difficulties to transcode and its happening during a waiting of transcode with the spiner on the center of the screen.

If you quit or back in chrome or whatever during this time, bam the process ffmpeg stays forever...

If you do that, the cpu is used at 100% and I have to kill each process with ssh :/.

Other usecase, you play a movie and if you rename it or remove it on HDD during this playback, sometimes same issue with ffmpeg which is lost, crash but the process stays.

 

By consequences, you got multiples processes.

 

I don't have this issue often, in fact, I avoid to quit the playback in the browser if there is a loading time ')

 

Hopping this explain can help

Edited September 26, 2019 by theghost31

[zyfinity 15]

This issue seems to have fixed itself in the latest beta from what i can see.

[theghost31 4]

OK I updated with the latest beta, I will advise with that .thx for the info.

[zyfinity 15]

The issue persists in the beta and stable updates so i really dont know what to do for it to work correctly.

[Luke 42085]

@@softworkz

[zyfinity 15]

sorry i think i got mixed up with another forum thread, but the beta seems to have definetly improve this issue as i used to see around 5 random ffmpeg tasks open but now it seems after using the beta for a around a week i only had 1 random ffmpeg task open. 

so i think there might be a bit more work needed but for the most part it seems to be working much much better in the beta.

although another issue mentioned in another thread is still persistant and thats the intel quicksync decoder not working and it seems to be the same for other people aswell.