Mach port leakage
Mach port leakage
- Subject: Mach port leakage
- From: Nathan Herring <email@hidden>
- Date: Thu, 12 Aug 2010 15:22:22 +0000
- Thread-topic: Mach port leakage
I'm trying to track down a case where we appear to be leaking Mach ports,
and have a repro case where if our code is called via [self
performSelectorInBackground:@selector(myCode) withObject:nil], we appear
(via the Activity Monitor) to leak exactly one port. This doesn't occur if
it happens on the main thread, and it doesn't occur with other calls. :/
I've tried using Instruments and a custom DTrace command to log calls to
mach_port_allocate(_qos|_full)?, mach_port_destroy, and mach_port_deallocate
to see if I can figure out the culprit, but it doesn't appear to show up.
Plus there're a bunch of calls to mach_port_deallocate that don't seem to
have a matching allocate (which is a different problem). Am I missing some
major mechanisms for ports to be called into existence or destroyed?
Thanks in advance,
nh
--
Nathan Herring
com.microsoft.devdiv.clr.os/development
_______________________________________________
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