I had a parallel thread on the dtrace list to get memleak.d running
http://blogs.sun.com/sanjeevb/date/200506
- I just got this stack trace from a 10 second sample of the most actively growing python mailman process - the output is explained by Sanjeev on his blog, but I'm hoping the stack trace will point the analysis towards a cause for why my mailman processes are growing abnormally
I will see if the findleaks.pl analysis of this output returns anything
Thanks!
0 42246 realloc:return Ptr=0x824c268 Oldptr=0x0 Size=16
libc.so.1realloc+0x33a pythonaddcleanup+0x45
pythonconvertsimple+0x145d pythonvgetargs1+0x259
python_PyArg_ParseTuple_SizeT+0x1d pythonposix_listdir+0x55
pythonPyEval_EvalFrameEx+0x59ff pythonPyEval_EvalCodeEx+0x57f
pythonPyEval_EvalFrameEx+0x49ff pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalCodeEx+0x57f pythonPyEval_EvalCode+0x22
pythonPyRun_FileExFlags+0xaf pythonPyRun_SimpleFileExFlags+0x156
pythonPy_Main+0xa6b pythonmain+0x17
python`_start+0x80
0 42249 free:entry Ptr=0x824c268
0 42244 lmalloc:return Ptr=0xcf890300 Size=16
libc.so.1lmalloc+0x143 libc.so.1opendir+0x3e
pythonposix_listdir+0x6d pythonPyEval_EvalFrameEx+0x59ff
pythonPyEval_EvalCodeEx+0x57f pythonPyEval_EvalFrameEx+0x49ff
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalCodeEx+0x57f
pythonPyEval_EvalCode+0x22 pythonPyRun_FileExFlags+0xaf
pythonPyRun_SimpleFileExFlags+0x156 pythonPy_Main+0xa6b
pythonmain+0x17 python_start+0x80
0 42244 lmalloc:return Ptr=0xcf894000 Size=8192
libc.so.1lmalloc+0x143 libc.so.1opendir+0x3e
pythonposix_listdir+0x6d pythonPyEval_EvalFrameEx+0x59ff
pythonPyEval_EvalCodeEx+0x57f pythonPyEval_EvalFrameEx+0x49ff
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalCodeEx+0x57f
pythonPyEval_EvalCode+0x22 pythonPyRun_FileExFlags+0xaf
pythonPyRun_SimpleFileExFlags+0x156 pythonPy_Main+0xa6b
pythonmain+0x17 python_start+0x80
0 42249 free:entry Ptr=0x86d78f0
^C
0 42246 realloc:return Ptr=0x824c268 Oldptr=0x0 Size=16
libc.so.1realloc+0x33a pythonaddcleanup+0x45
pythonconvertsimple+0x145d pythonvgetargs1+0x259
python_PyArg_ParseTuple_SizeT+0x1d pythonposix_listdir+0x55
pythonPyEval_EvalFrameEx+0x59ff pythonPyEval_EvalCodeEx+0x57f
pythonPyEval_EvalFrameEx+0x49ff pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalCodeEx+0x57f pythonPyEval_EvalCode+0x22
pythonPyRun_FileExFlags+0xaf pythonPyRun_SimpleFileExFlags+0x156
pythonPy_Main+0xa6b pythonmain+0x17
python`_start+0x80
0 42249 free:entry Ptr=0x824c268
0 42244 lmalloc:return Ptr=0xcf890300 Size=16
libc.so.1lmalloc+0x143 libc.so.1opendir+0x3e
pythonposix_listdir+0x6d pythonPyEval_EvalFrameEx+0x59ff
pythonPyEval_EvalCodeEx+0x57f pythonPyEval_EvalFrameEx+0x49ff
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalCodeEx+0x57f
pythonPyEval_EvalCode+0x22 pythonPyRun_FileExFlags+0xaf
pythonPyRun_SimpleFileExFlags+0x156 pythonPy_Main+0xa6b
pythonmain+0x17 python_start+0x80
0 42244 lmalloc:return Ptr=0xcf894000 Size=8192
libc.so.1lmalloc+0x143 libc.so.1opendir+0x3e
pythonposix_listdir+0x6d pythonPyEval_EvalFrameEx+0x59ff
pythonPyEval_EvalCodeEx+0x57f pythonPyEval_EvalFrameEx+0x49ff
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalFrameEx+0x6133
pythonPyEval_EvalFrameEx+0x6133 pythonPyEval_EvalCodeEx+0x57f
pythonPyEval_EvalCode+0x22 pythonPyRun_FileExFlags+0xaf
pythonPyRun_SimpleFileExFlags+0x156 pythonPy_Main+0xa6b
pythonmain+0x17 python_start+0x80
0 42249 free:entry Ptr=0x86d78f0
On 7/2/08 10:14 AM, "Barry Warsaw" <barry@list.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jul 2, 2008, at 1:12 PM, Fletcher Cocquyt wrote:
I am hopeful our esteemed code maintainers are thinking the built in restart idea is a good one:
Optionally, yes. By default, I'm not so sure.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkhrt4UACgkQ2YZpQepbvXE9kACeLg04R4n22C4X3VInoJaaCqyI MdkAoJjgj0qwONIKM425QHh/Glxpo4gm =yOaG -----END PGP SIGNATURE-----
-- Fletcher Cocquyt Senior Systems Administrator Information Resources and Technology (IRT) Stanford University School of Medicine
Email: fcocquyt@stanford.edu Phone: (650) 724-7485