I've been dealing with mem leaks when i started setting up the streams, i used video and audio stream, video streaming through gstreamer onto nginx rtmp, and audio streaming to icecast, a few things has caused mem leaks in my case and it was quite the pain in discovering it.
When using the same playlist for fallback, i believe this is causing mem leaks because, when there's the error "broken" file is the same file in the playlist as it's loading same playlist on fallback. skip_blank has been messing around with mem leaks and files also, this was specific for video streams, sometimes out of no reason, it cuts videos at the same specific time every time. And lastly try using only OGG file format. I found out that only OGG file formats don't increase mem size and have the stream running stable for weeks now. This is the case for both video and audio stream, but for video is much more noticeable than audio. Audio stream can take days before significantly increase mem usage, while video take a day. On Mon, Mar 1, 2021 at 8:32 PM p····· g······· <pra...@gmail.com> wrote: > sorry to mash all this under one subject, but as it started so, let it > finish.. my last observation about win memleak by adding lines to test.liq > config i've posted today: > if i take that input.harbor line out from the config: > harb = input.harbor(id="harb", buffer=30.,max=90.,"harb", port=8010, > password="xxx") > > and therefore also change > radio = fallback(track_sensitive=false, [harb, playlyst]) to > radio = fallback(track_sensitive=false, [s, playlyst]) (because ther is no > 'harb' anymore - so let it have new orleans radio instead) > > the leak seems not to occur... > > Pranas > > > > -----Original Message----- > From: Romain Beauxis > Date: 2021 m. kovo 1 d. 04:47 > To: savonet-users > Subject: Re: [Savonet-users] Liquidsoap 1.4.4 is out! > > > Hi all, > > > We've been aware of these issues with the windows build but haven't been > able to reproduce so far and also haven't had many more similar reports. > > Of course, we are always willing to fix an issue like this one but at the > moment, there isn't much clue about what's causing it. It seems that such > a > massive memory leak should be either something that would also happen in > the > linux version of the application or else something that is coming from the > cross-compiler itself. > > Romain > > > > _______________________________________________ > Savonet-users mailing list > Savonet-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/savonet-users >
_______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
