FFMPEG temporarily eating a lot of memory after every reboot
Posted: Tue Apr 07, 2015 7:15 am
I've been noticing this since at least the 4.x versions through the current version.
The first time I open UMS after rebooting, it spawns a ffmpeg process that proceeds to us 3.5 GB of RAM going through my fonts. I suspect it's building a font cache, and after it's done it goes away and does not recur on subsequent launches until I reboot the computer. Shouldn't the font cache persist between reboots as well unless it detects a change to installed fonts?
Also, I do not have ffmpeg enabled at all in my transcoding settings, so shouldn't it also detect if it's even being used before automatically running and eating up a ton of RAM.
Just something I wanted to point out in case a more persistent caching could be implemented or it could not load at all if not being used.
The first time I open UMS after rebooting, it spawns a ffmpeg process that proceeds to us 3.5 GB of RAM going through my fonts. I suspect it's building a font cache, and after it's done it goes away and does not recur on subsequent launches until I reboot the computer. Shouldn't the font cache persist between reboots as well unless it detects a change to installed fonts?
Also, I do not have ffmpeg enabled at all in my transcoding settings, so shouldn't it also detect if it's even being used before automatically running and eating up a ton of RAM.
Just something I wanted to point out in case a more persistent caching could be implemented or it could not load at all if not being used.