On Mar 17, 2008, at 4:25 PM, Andy Klepack wrote:
I'm seeing this problem in some AE handlers installed via AEInstallEventHandler. There are no warnings about a pool not existing, but the app memory usage grows and grows. Wrapping the handler in a pool creation and release appears to solve this.
Your question is valid, and you appear to have found the answer for yourself. Just one FYI:
Have you considered using -[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:] instead of AEInstallEventHandler? I suspect Cocoa will take care of the autorelease pool for you in that case.
Cheers, Ken _______________________________________________ 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)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
