what is meant by "autoreleased with no pool in place - just leaking"???

Question

Level 2

200 points

what is meant by "autoreleased with no pool in place - just leaking"???

What does this mean??? When MagiCal is running I get this chronically in the system log...

Sep 1 19:51:26 paris3 MagiCal[191]: * __NSAutoreleaseNoPool(): Object 0x1b95c550 of class NSCustomReleaseData autoreleased with no pool in place - just leaking
Sep 1 19:51:26 paris3 MagiCal[191]: * __NSAutoreleaseNoPool(): Object 0x15377e70 of class __NSArray0 autoreleased with no pool in place - just leaking
Sep 1 19:51:26 paris3 MagiCal[191]: * __NSAutoreleaseNoPool(): Object 0x153b5360 of class NSImage autoreleased with no pool in place - just leaking
Sep 1 19:51:26 paris3 MagiCal[191]: * __NSAutoreleaseNoPool(): Object 0x1b95b500 of class NSBitmapImageRep autoreleased with no pool in place - just leaking
Sep 1 19:51:26 paris3 MagiCal[191]: * __NSAutoreleaseNoPool(): Object 0x1b95c580 of class NSImage autoreleased with no pool in place - just leaking
Sep 1 19:51:27: --- last message repeated 1 time ---
Sep 1 19:51:27 paris3 MagiCal[191]: * __NSAutoreleaseNoPool(): Object 0x1ac90b20 of class NSCustomReleaseData autoreleased with no pool in place - just leaking

What does it mean??? I assume it is a problem or is at least tying up resources??? Any feedback would be much appreciated...

thanks... bob...

FW800 G4 dual 1.25 Ghz and two each 17 inch MacBook Pros, Mac OS X (10.6)

Posted on Sep 1, 2009 7:59 PM

Reply

Answer 1

Best reply

edclange

Level 5

4,374 points

Sep 1, 2009 8:45 PM in response to Robert Paris

It means that whoever makes MagiCal probably needs to fix their memory management. Sounds like it spawned a new thread without setting up a new autorelease pool for that thread.

For you, it means that MagiCal has a memory leak, and that you'll slowly lose free memory while using it. If you only run this app occasionally, it's no big deal. If it's running all the time, then you should restart it every few hours or days.

Reply

Answer 2

Robert Paris Author

Level 2

200 points

Sep 2, 2009 8:21 AM in response to edclange

Thanks... I suspected it was something like what you said... There was another clock utility I've been looking at and I decided to give it a shot last night... No more memory leak messages now... thanks again... bob...

Reply

Answer 3

edclange

Level 5

4,374 points

Sep 2, 2009 9:28 AM in response to Robert Paris

Thanks for the "Solved" star.

Even if you're not going to use this MagiCal app, I'd suggest shooting its developers an e-mail with your log messages and findings. If it needs to be fixed, and their testers haven't tried the combination of options that caused your problem, they'll appreciate your input.

Reply

Answer 4

Robert Paris Author

Level 2

200 points

Sep 2, 2009 5:28 PM in response to edclange

As you suggested I went to the developer site and folks have already reported this "leaking" problem... They are reporting that it started with Snow Leopard and I would guess that is correct... I can't say for sure but I do look at the system log often enough that had this been going on with Leopard I likely would have noticed it... Anyway, the developer is aware (now). Thanks for your help... bob...

Reply