Hi,
In case you're not receiving notifications, I believe I fixed the
issue, in branch LS-132.
This makes me realize that funny things will happen in the sort of
situation we're considering. If an active source is attached to the
inner clock of cue_cut, it only lives through cue_cut, who is
thanks david,
apparently these are the clocks of smart_cross and cue_cut that are not
destroyed. but the problem is that the shutting down of their connected
sources does not make those clocks go away, apparently.
1) For example, as soon as the application starts, I have those clocks
running
Hi,
Good catch, I confirm the issue! cue_cut (and probably also cross and
smart_cross) operators are garbage collected but leave their clock
behind. Something is preventing those from being claimed by the GC.
I have created an issue on github:
https://github.com/savonet/liquidsoap/issues/132
Big thanks!
On 16/11/2013 23:19, David Baelde wrote:
Hi,
Good catch, I confirm the issue! cue_cut (and probably also cross and
smart_cross) operators are garbage collected but leave their clock
behind. Something is preventing those from being claimed by the GC.
I have created an issue on
Hi,
On Tue, Nov 12, 2013 at 10:13 PM, okay_awright okay_awri...@ddcr.biz wrote:
When you say crossing operators do you mean functions that need at
least two sources to operate like fallback() etc or more like add() and
the like?
I meant cross(), smart_cross() and what's derived from them.
Hi,
In principle unused clocks should be garbage collected. This may take
some time, but you can try to trigger it using the garbage_collect()
builtin.
I'm interested in investigating this issue if you're still puzzled by
it, but I would need a simple script to play with. You must be using
more
Hello
I've already tried to force the garbage collection but apparently either
it doesn't work right away or it means that those clocks are still in
use because the number of clocks doesn't decrease after calling that
function.
My full example might not be trivial indeed. Here's what I'm
Hello,
I have a problem related to the number of clocks that keeps growing and
never decreases or remain stable.
Here's my setup, in a few words:
1) Create an output.icecast (i.e. ref_source := output.icecast(...))
iff an error occurs:
2) Destroy that active_source (i.e.