• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: memory use / embedding concerns
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: memory use / embedding concerns


  • Subject: Re: memory use / embedding concerns
  • From: Andre Schnoor <email@hidden>
  • Date: Mon, 14 Sep 2009 12:44:56 +0200

Am 13.09.2009 um 21:14 schrieb John Clements:

I'm trying to embed CoreAudio functionality in a system (mzscheme) that uses precise garbage collection. In order to do this successfully, I need to be able to identify the blocks of memory allocated by the CoreAudio library, and walk them for pointers to other pointers.

John,

walking external (FFI-connected) structures for pointers sounds like a very dangerous idea to me.

I strongly recommend to treat the AUGraph as an opaque object that is not subject to the host language's garbage collection at all. Instead it should be closed and released explicitly when no longer needed (similar to external files, network connections, and the like).

If PLT Scheme supports finalization of objects, you could hook up the closing of the AUGraph to that. This would care about the proper closing cleanup automatically when a Scheme object becomes unreferenced.

Andre

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >memory use / embedding concerns (From: John Clements <email@hidden>)

  • Prev by Date: Re: memory use / embedding concerns
  • Next by Date: set spatialization algorithm for AU3DMixerEmbedded
  • Previous by thread: Re: memory use / embedding concerns
  • Next by thread: Re: memory use / embedding concerns
  • Index(es):
    • Date
    • Thread