Lists

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

Re: Leaking Mach Ports?

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

Re: Leaking Mach Ports?

Subject: Re: Leaking Mach Ports?
From: Matt Watson <email@hidden>
Date: Fri, 11 Mar 2005 12:48:37 -0800

I seem to recall that you have to call mach_port_deallocate() for any port returned from mach_thread_self()...Are you doing that?

No one should be using mach_thread_self(), unless you are creating raw mach threads. Use pthread_mach_thread_np() instead. This does not require a mach_port_deallocate().

I believe the port leak being seen here is normal, as a thread port remains after the thread is detached, to be cleaned up by the next pthread_create() or pthread_exit() that is called.

matt.

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


Follow-Ups:

Re: Leaking Mach Ports?
From: Dirk Musfeldt <email@hidden>


References:  
  >Re: Leaking Mach Ports? (From: Dirk Musfeldt <email@hidden>)
  >Re: Leaking Mach Ports? (From: Chris Sarcone <email@hidden>)




Prev by Date:
Re: Leaking Mach Ports?

Next by Date:
Re: Leaking Mach Ports?

Previous by thread:
Re: Leaking Mach Ports?

Next by thread:
Re: Leaking Mach Ports?

Index(es):

Date
Thread