Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Video playback: excessive memory usage #318

Closed
sebleblanc opened this issue Apr 14, 2016 · 3 comments
Closed

Video playback: excessive memory usage #318

sebleblanc opened this issue Apr 14, 2016 · 3 comments
Labels

Comments

@sebleblanc
Copy link

I was testing video playback (using the GStreamer audio-video output) and left it running overnight. When I came back to my computer, I noticed that Liquidsoap was not running anymore. Looking at logs, the OOM killer was invoked after about 5 hours of playback. I have 16GB of memory on this system, so that is quite a lot of memory to use, for a simple looped video script.

Running that script for 15 minutes shows that it already uses 3.6G of resident memory, 11.4G of virtual memory.

Here is my (very simple) script:

background = fallback([single("./samples/videos/fireplace.mp4"), blank()])
queue = request.queue(id="request")

program = fallback(track_sensitive=false,
                   [queue, background])

output.gstreamer.audio_video(program)
@S54B32
Copy link

S54B32 commented Apr 14, 2016

Test your script without using a fallback to blank. I have seen generating blank cause issues in the past (with audio scripts).

It might not have any effect but worth trying.

Also it would be helpful to know which version of Liquidsoap you're running.

@toots
Copy link
Member

toots commented Apr 27, 2017

Is there any chance that you could try with a recent liquidsoap version compiled with gstreamer builtin (not as a plugin)? The opam install instructions should provide a quick way to get there: http://liquidsoap.fm/download.html

I'm asking b/c the bug might be fixed in the recent code and also the plugin build is now deprecated in favor of opam.

@toots
Copy link
Member

toots commented Aug 20, 2018

This should be fixed now!

@toots toots closed this as completed Aug 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants