Bug #53959 A Leak in MEM Service Manager in the _NSAutoreleaseNoPool() method
Submitted: 25 May 2010 6:17 Modified: 25 May 2010 13:56
Reporter: Jonathon Coombes Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Enterprise Monitor: Server Severity:S2 (Serious)
Version:2.2.0.1651 OS:MacOS (Mac OS X 10.5)
Assigned to: Andy Bang CPU Architecture:Any
Tags: Leak, mem, memory leak, Merlin

[25 May 2010 6:17] Jonathon Coombes
Description:
Have been testing MEM with LDAP authentication and found the following in the log file:

2010-05-18 14:18:05.361 java[39880:10b] *** _NSAutoreleaseNoPool(): Object 0x140137440 of class NSConcreteMapTableValueEnumerator autoreleased with no pool in place - just leaking
Stack: (0x7fff8467f1e8 0x7fff84597771 0x7fff8316556e 0x7fff808cf187 0x7fff80f66bd8 0x7fff80f66cd0 0x7fff80f623e7 0x7fff80f8412c 0x100003d12 0x10000374d 0x100001154)
2010-05-19 21:56:07.014 java[39880:10b] *** _NSAutoreleaseNoPool(): Object 0x140139fc0 of class NSConcreteMapTableValueEnumerator autoreleased with no pool in place - just leaking
Stack: (0x7fff8467f1e8 0x7fff84597771 0x7fff8316556e 0x7fff808cf187 0x7fff80f66bd8 0x7fff80f66cd0 0x7fff80f623e7 0x7fff80f8412c 0x100003d12 0x10000374d 0x100001154)
2010-05-20 21:58:33.398 java[39880:10b] *** _NSAutoreleaseNoPool(): Object 0x100149740 of class NSConcreteMapTableValueEnumerator autoreleased with no pool in place - just leaking
Stack: (0x7fff8467f1e8 0x7fff84597771 0x7fff8316556e 0x7fff808cf187 0x7fff80f66bd8 0x7fff80f66cd0 0x7fff80f623e7 0x7fff80f8412c 0x100003d12 0x10000374d 0x100001154)
2010-05-22 14:58:41.233 java[39880:10b] *** _NSAutoreleaseNoPool(): Object 0x14015dd40 of class NSConcreteMapTableValueEnumerator autoreleased with no pool in place - just leaking
Stack: (0x7fff8467f1e8 0x7fff84597771 0x7fff8316556e 0x7fff808cf187 0x7fff80f66bd8 0x7fff80f66cd0 0x7fff80f623e7 0x7fff80f8412c 0x100003d12 0x10000374d 0x100001154)
2010-05-22 21:30:55.447 java[39880:10b] *** _NSAutoreleaseNoPool(): Object 0x14013f3f0 of class NSConcreteMapTableValueEnumerator autoreleased with no pool in place - just leaking
Stack: (0x7fff8467f1e8 0x7fff84597771 0x7fff8316556e 0x7fff808cf187 0x7fff80f66bd8 0x7fff80f66cd0 0x7fff80f623e7 0x7fff80f8412c 0x100003d12 0x10000374d 0x100001154)

How to repeat:
Not sure if it is triggered by anything in particular.

Suggested fix:
Stop the automatic release or look at why there is no pool.
[25 May 2010 13:56] Enterprise Tools JIRA Robot
Mark Matthews writes: 
These are log messages from Mac OS/X native framework classes, not service manager code. Watch "console" long enough and just about every native application will have them. If there's a bug to be filed, it's against Apple's implementation of the Java VM.