it's me again about flac-less config memory leak.
so, earlier today i wrote that i got memory leaking after connecting via
telnet. i did that twice and observed the outcome.
so, after connecting and disconnecting via telnet the memory usage grows but
eventually stops. then on second connect /
bad news. or maybe good news, that it's not just flac-bound.
i eliminated ogg flac output in my config (i've sent it to Romain at some
point, my whole config), restarted process, let it run for half an hour,
connected via telnet and it started leaking.
regards,
p
Hi, Romain!
Oh yeah, so it's not then that the windows compiler sucks.
Well, I have another radio running which does not leak and does not use
flac, BUT being lossless is my main point... the one and only lossless radio
nation wide and hell knows, maybe in whole baltics :)
if i used
Ok, I can confirm that I see a mem leak when receiving a ogg/flac stream on
the harbor. It is not just on windows but can be reproduced on OSX and
linux.
>From what I can see, the mem leak is not obvious and could be related to
some sort of stack corruption, which would explain the other issues
I was able to make it work and reproduce. Stay tuned!
Le jeu. 24 janv. 2019 à 12:18, p· g··· a écrit :
> hmm, it does. if it doesn't maybe try exiting and starting encoder again,
> second connect should go through.
> are you using altacast from my link? another versions might be buggy
hmm, it does. if it doesn't maybe try exiting and starting encoder again,
second connect should go through.
are you using altacast from my link? another versions might be buggy and not
work, i remember it was a long process for me to find a working flac streamer...
when it works, it should show
Ok, first remark: when using altacast with Ogg FLAC, input.harbor fails
with the following log:
[input(dot)harbor_6707:2] Feeding stopped: Ogg_demuxer.Invalid_stream.
Does it work for you?
Le mer. 23 janv. 2019 à 15:55, p g a écrit :
> hi, Romain and thanks for the new build!
> It started
Thanks, that's helpful. Investigating now.
Le mer. 23 janv. 2019 à 15:55, p g a écrit :
> hi, Romain and thanks for the new build!
> It started leaking right away! the same moment i click CONNECT in altacast
> encoder, it starts leaking memory at liquidsoap process on server.
> i've cut the
hi, Romain and thanks for the new build!
It started leaking right away! the same moment i click CONNECT in altacast
encoder, it starts leaking memory at liquidsoap process on server.
i've cut the config short, as it's enough to reproduce. it doesn't have to
be strip_blank, it can be an
Hey,
Could you try the 1.3.6 release for windows? It contains several fixes,
including some related to the flac encoder which I think I remember you are
using in your script.
It's here: https://github.com/savonet/liquidsoap/releases/tag/1.3.6
Thanks,
Romain
Le mar. 22 janv. 2019 à 10:17,
Hi,
Le mar. 22 janv. 2019 à 07:13, p g a écrit :
> i have a recipe for an easy leak!
>
> start the process, let it run for while playing some playlist.. for an
hour
> or so...
> then connect via telnet to your liquidsoap and watch the process tickling
up
> your RAM!
Unfortunately, this still
11 matches
Mail list logo
