• 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: hiccups in AUGraph
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hiccups in AUGraph


  • Subject: Re: hiccups in AUGraph
  • From: Gregory Wieber <email@hidden>
  • Date: Wed, 20 Oct 2010 10:10:31 -0700

If you overload the CPU during an IO Proc,  would that cause app crashes?  I thought if anything,  attempting to do to much processing would cause pops, clicks, missed callbacks,  but I'm getting some crashes occasionally and I haven't isolated the issue yet.  (I'm using performance tools to test for the obvious like leaks, etc).

I've probably more optimization left to do;  tried to make sure every variable is a pointer, tried minimizing conditionals,  etc...  When you say allocating memory is bad,  do you mean at all?  Is it important enough that I should dig through my render callbacks and make sure absolutely every last variable is a pointer and not created during the callback?  

 _______________________________________________
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

  • Follow-Ups:
    • Re: hiccups in AUGraph
      • From: William Stewart <email@hidden>
References: 
 >hiccups in AUGraph (From: Sanoj Nambi <email@hidden>)
 >Re: hiccups in AUGraph (From: James McCartney <email@hidden>)

  • Prev by Date: Re: Why is CoreAudio C++ not Objective-C?
  • Next by Date: getting to grips with coreaudio
  • Previous by thread: Re: hiccups in AUGraph
  • Next by thread: Re: hiccups in AUGraph
  • Index(es):
    • Date
    • Thread