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 going to do: 1) remove all "crossing operators" from the scripts and 2) make sure that all output.something are properly shut down when not needed anymore (I thought I already did that though.) 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? Do I need to watch out for other potential tricky commands and corner cases? If it still doesn't work I'll try to trim and prune those scripts to the maximum for further auditing by the mailing list readers maybe. I also use once or twice some output.dummy in order to get hold of a reference I would later use, if I recycle that reference (I replace its associated value by another output.something(source)) does that old reference and its corresponding clock get garbage collected or a do I absolutely need to issue a source.shutdown() on top of it beforehand? Thanks again for your ever precious help. On 12/11/2013 10:05, David Baelde wrote: > 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 than icecast, otherwise only the default wallclock would be > involved. Perhaps crossing operators? > > Cheers, > > David > > On Mon, Nov 4, 2013 at 1:58 AM, okay_awright <okay_awri...@ddcr.biz> wrote: >> 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. source.shutdown(!ref_source)) >> 3) go back to 1) >> >> It works fine, but apparently the number of assigned clocks keeps >> growing after each cycle (according to the logs), but that number should >> remain stable in my case, right? >> Will the garbage collector take care of the unused sources later on? >> >> Do you have advices on how to troubleshoot this problem? >> Is source.shutdown() enough to guarantee that any clock used by this >> active source will be freed? >> >> -- >> regards, >> okay_awright >> <okay_awright AT ddcr DOT biz> >> >> ------------------------------------------------------------------------------ >> Android is increasing in popularity, but the open development platform that >> developers love is also attractive to malware creators. Download this white >> paper to learn more about secure code signing practices that can help keep >> Android apps secure. >> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >> _______________________________________________ >> Savonet-users mailing list >> Savonet-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/savonet-users > > > -- regards, okay_awright <okay_awright AT ddcr DOT biz> ------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk _______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
