Kirk Kerekes wrote:
Use Activity Monitor (or other tool of your choice) to check for a
port leak.
It wasn't that...
Turns out that the protocol on the connection had a call which took an
Objective C object as a parameter. The parameter wasn't declared as
/byref/ or /bycopy/, so I believe it
Use Activity Monitor (or other tool of your choice) to check for a
port leak.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)l
Aurélien Hugelé wrote:
Are you sure you are not instantiating/creating/opening a connection
each time? are you really reusing the same connection?
Yes. There's a lot of logging around that code. If it was being closed
and re-opened we'd see it. I've also debugged through that code, and
the i
Are you sure you are not instantiating/creating/opening a connection
each time? are you really reusing the same connection?
Aurélien,
Objective Decision Team
On 2 juil. 09, at 21:29, Kevin Brock wrote:
We've got an application that uses some NSConnection objects to call
between binaries
We've got an application that uses some NSConnection objects to call
between binaries. An application calls interfaces of an object which is
vended by a daemon.
The calls between modules are made frequently, and during some testing I
noticed a steady drop in perfomance of the application. I
