According to instruments, this seems to be working fine. Thanks.
On Oct 22, 2011, at 12:42 PM, Jean-Daniel Dupas wrote:
> I also encounter this annoying issue, and also try something like that, but
> as you can see, it does not works.
>
> I workaround this issue by periodically posting applicat
I only glanced over the details of your problem, so forgive me if this is way
off.
I solved the memory ballooning issue in a background app by posting an
"NSApplicationDefined" NSEvent (with zeros for all the arguments), which causes
the NSApplication loop to return from -nextEventMatchingMask
I also encounter this annoying issue, and also try something like that, but as
you can see, it does not works.
I workaround this issue by periodically posting application defined event that
trigger an event loop, and make the framework drain the autorelease pool.
Somewhere in my application ini
On Oct 22, 2011, at 8:53 AM, Mr. Gecko wrote:
> static NSAutoreleasePool *pool = nil;
>
> void runloop(CFRunLoopObserverRef observer, CFRunLoopActivity activity, void
> *info) {
> if (activity & kCFRunLoopEntry) {
> if (pool!=nil) [pool drain];
> pool = [NSAutor
Hello, I have a problem with 10.7 where when you drag files to a view which
accepts files, it'll crash because of a leak of some sort. This is triggered by
my CFRunLoopObserver which I've written because operations which is done in the
background never had the autorelease pool drained until the
