[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-users] Freeing Previously Allocated Busses
- To: sc-users@xxxxxxxxxxxxxxxx
- Subject: Re: [sc-users] Freeing Previously Allocated Busses
- From: James Harkins <jamshark70@xxxxxxxxx>
- Date: Wed, 6 May 2009 17:36:19 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=tSGfm/4yLEGFw3cuhvVa5ctI4pjfHeRA7IaD1mDbQt0=; b=kEeVeXk7y0MIvkzADzAYZfeiMmefpBUdJkwZb8Qcf6YJIEQLEq6dq50rtIz1Mh3XCX l5b//HnMiKgkuFPhvhpMv3zni476vrYIvrFJVRDseAxLtOSDsvmglc9lLD0EZmQJeJgx 2lVSPwzFT1cn7MIfsen7b2VDJVdL+C7M7HJKQ=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; b=gQQ6Xryqi8qqSQ2M0wTbcsUzqr8j+mjZC5NVzXSXta/Uxcpp0/K2OKyU6L1F7yv4Iu yYjBj9Q6nAyDvIXL+blEScy8Mi/cR3emWAkX5dQq+AdgkNnxoNQw/6UAgqoKenpwFB0y Z4B3JEyySNHz1W0S9cfkjSvdvkA4ztxY0aOLo=
- In-reply-to: <59485.68.228.99.237.1241615321.squirrel@xxxxxxxxxxxxxxxxxxxxx>
- List-id: SuperCollider users mailing list <sc-users.create.ucsb.edu>
- References: <59485.68.228.99.237.1241615321.squirrel@xxxxxxxxxxxxxxxxxxxxx>
- Reply-to: sc-users@xxxxxxxxxxxxxxxx
- Sender: owner-sc-users@xxxxxxxxxxxxxxxx
On Wed, May 6, 2009 at 9:08 AM, <koonce@xxxxxxxxxxxxx> wrote:
> What is the simplest way of freeing all allocated busses from a previous,
> terminated process? Sudden termination leaves no record of the allocated
> bus objects, so I can't see how to free them.
>
> Similarly, is there a way to list the currently assigned/allocated busses
> so that I may then free them?
Nope. It's the user's responsibility to track them.
This kind of issue is exactly why I wrote PR/BP in the ddwChucklib
quark. There, you have a Process object that encompasses both the
behavior AND any resources it uses (including buses). Terminating the
process doesn't kill the process (remove it from memory) -- you
explicitly free it, and at that time, the process removes its
resources.
Processes are kept in a global collection for you so it's a lot harder
to lose track of them.
PR/BP is a pretty open framework with lots of options, but the basic
principles are simple.
hjh
--
James Harkins /// dewdrop world
jamshark70@xxxxxxxxxxxxxxxxx
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
_______________________________________________
sc-users mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/