Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

HAL Thread question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

HAL Thread question

Subject: HAL Thread question
From: Craig Hopson <email@hidden>
Date: Tue, 18 Apr 2006 09:03:44 -0600

Can someone give me a quick thread sanity check...

I start my app and attach Thread Viewer. I have one thread, the main loop, running. I do whatever setup and hit Play. I now have three more threads running: the HAL thread a high priority I/O thread my internal processing thread I hit Stop. At this point I: call MusicPlayerStop stop, disconnect, and dispose of my processor(s) (They are terminal, so the AUGraph remains in tact.) call DisposeMusicPlayer call DisposeMusicSequence My processor thread and the I/O thread go away, but the HAL thread stays around (waiting in run loop). Is this normal? When I Play again, I do not get a new HAL thread. Once created, does the HAL thread hang around ? Or, am I missing something in my tear down? It doesn't seem to be a problem (now), I'm just curious if this is expected behavior or if I need to look for something in my code.

Thanks.

Craig Hopson
Red Rock Software

_______________________________________________
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: HAL Thread question
From: Jeff Moore <email@hidden>


Prev by Date:
siCompressionParams Question

Next by Date:
Re: AU state & MaximumFramesPerSlice

Previous by thread:
Re: siCompressionParams Question

Next by thread:
Re: HAL Thread question

Index(es):

Date
Thread