I'm getting out of memory errors and I'm not sure how to begin diagnosing this. They start very quickly after Unraid starts the array. I have managed to tie it to Docker so I suspect one of the Docker containers is going haywire. For now, I have Docker running but none of the containers. I'm not sure where to go from here though. Can anyone provide suggestions?

marvin-diagnostics-20250909-1815.zip

10 hours ago, skoberlink said:

I'm getting out of memory errors and I'm not sure how to begin diagnosing this. They start very quickly after Unraid starts the array. I have managed to tie it to Docker so I suspect one of the Docker containers is going haywire. For now, I have Docker running but none of the containers. I'm not sure where to go from here though. Can anyone provide suggestions?

marvin-diagnostics-20250909-1815.zip

One of your containers is firing off a bunch of ffmpeg processes, so if you have one that's converting media then change its config so it caches to disk instead of RAM

1 hour ago, Michael_P said:

One of your containers is firing off a bunch of ffmpeg processes, so if you have one that's converting media then change its config so it caches to disk instead of RAM

That would be FileFlows and sure enough, I can start all the other containers without issue. So at least I'm running stable again. Thanks!

I've had FileFlows running for a few months without issues. I have a temp directory configured on the cache drive for transcodes, as described in the documentation. I don't see anyone reporting issues here or on GitHub. The last update was a week or two ago and it's been able to convert other files since then.

I know this is not an ffmpeg or FileFlows support forum but on the off-chance someone here also knows that technology, is there something about a given file that could make it not use the temp directory or otherwise eat up memory like this?

All depends on your configuration you haven't mentioned. Help with that should probably be in the support thread for the container you're using.

Edited September 10, 2025Sep 10 by Kilrah

4 hours ago, skoberlink said:

I've had FileFlows running for a few months without issues. I have a temp directory configured on the cache drive for transcodes, as described in the documentation

It could be that it's been operating within available RAM the whole time, and then tried to do too much at once. Double check to make sure the cache location is correctly mapped to disk. Also, reboot the server so the log is cleared and FCP stops warning you about the past OOMs