[Mailman-Users] Python process size grows 30x in 8 hours - dtrace stack
Fletcher Cocquyt
fcocquyt at stanford.edu
Wed Jul 2 23:16:34 CEST 2008
Below is the findleaks output from a ~5minute sample of a python runner - I
will take a larger sample to see if this is representative or not:
(again the reference is http://blogs.sun.com/sanjeevb/date/200506 )
Thanks
god at irt-smtp-02:~ 2:10pm 67 # ./findleaks.pl ./ml.out
Ptr=0xcf890340 Size=16
libc.so.1`lmalloc+0x143
libc.so.1`opendir+0x3e
python`posix_listdir+0x6d
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
---------
Ptr=0xcf894000 Size=8192
libc.so.1`lmalloc+0x143
libc.so.1`opendir+0x3e
python`posix_listdir+0x6d
python`PyEval_EvalFrameEx+0x59ff
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalFrameEx+0x49ff
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalFrameEx+0x6133
python`PyEval_EvalCodeEx+0x57f
python`PyEval_EvalCode+0x22
python`PyRun_FileExFlags+0xaf
python`PyRun_SimpleFileExFlags+0x156
python`Py_Main+0xa6b
python`main+0x17
python`_start+0x80
---------
On 7/2/08 1:54 PM, "Fletcher Cocquyt" <fcocquyt at stanford.edu> wrote:
> 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.1`realloc+0x33a
> python`addcleanup+0x45
> python`convertsimple+0x145d
> python`vgetargs1+0x259
> python`_PyArg_ParseTuple_SizeT+0x1d
> python`posix_listdir+0x55
> python`PyEval_EvalFrameEx+0x59ff
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalFrameEx+0x49ff
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalCode+0x22
> python`PyRun_FileExFlags+0xaf
> python`PyRun_SimpleFileExFlags+0x156
> python`Py_Main+0xa6b
> python`main+0x17
> python`_start+0x80
>
> 0 42249 free:entry Ptr=0x824c268
> 0 42244 lmalloc:return Ptr=0xcf890300 Size=16
> libc.so.1`lmalloc+0x143
> libc.so.1`opendir+0x3e
> python`posix_listdir+0x6d
> python`PyEval_EvalFrameEx+0x59ff
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalFrameEx+0x49ff
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalCode+0x22
> python`PyRun_FileExFlags+0xaf
> python`PyRun_SimpleFileExFlags+0x156
> python`Py_Main+0xa6b
> python`main+0x17
> python`_start+0x80
>
> 0 42244 lmalloc:return Ptr=0xcf894000 Size=8192
> libc.so.1`lmalloc+0x143
> libc.so.1`opendir+0x3e
> python`posix_listdir+0x6d
> python`PyEval_EvalFrameEx+0x59ff
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalFrameEx+0x49ff
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalCode+0x22
> python`PyRun_FileExFlags+0xaf
> python`PyRun_SimpleFileExFlags+0x156
> python`Py_Main+0xa6b
> python`main+0x17
> python`_start+0x80
>
> 0 42249 free:entry Ptr=0x86d78f0
> ^C
> 0 42246 realloc:return Ptr=0x824c268 Oldptr=0x0 Size=16
> libc.so.1`realloc+0x33a
> python`addcleanup+0x45
> python`convertsimple+0x145d
> python`vgetargs1+0x259
> python`_PyArg_ParseTuple_SizeT+0x1d
> python`posix_listdir+0x55
> python`PyEval_EvalFrameEx+0x59ff
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalFrameEx+0x49ff
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalCode+0x22
> python`PyRun_FileExFlags+0xaf
> python`PyRun_SimpleFileExFlags+0x156
> python`Py_Main+0xa6b
> python`main+0x17
> python`_start+0x80
>
> 0 42249 free:entry Ptr=0x824c268
> 0 42244 lmalloc:return Ptr=0xcf890300 Size=16
> libc.so.1`lmalloc+0x143
> libc.so.1`opendir+0x3e
> python`posix_listdir+0x6d
> python`PyEval_EvalFrameEx+0x59ff
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalFrameEx+0x49ff
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalCode+0x22
> python`PyRun_FileExFlags+0xaf
> python`PyRun_SimpleFileExFlags+0x156
> python`Py_Main+0xa6b
> python`main+0x17
> python`_start+0x80
>
> 0 42244 lmalloc:return Ptr=0xcf894000 Size=8192
> libc.so.1`lmalloc+0x143
> libc.so.1`opendir+0x3e
> python`posix_listdir+0x6d
> python`PyEval_EvalFrameEx+0x59ff
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalFrameEx+0x49ff
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalFrameEx+0x6133
> python`PyEval_EvalCodeEx+0x57f
> python`PyEval_EvalCode+0x22
> python`PyRun_FileExFlags+0xaf
> python`PyRun_SimpleFileExFlags+0x156
> python`Py_Main+0xa6b
> python`main+0x17
> python`_start+0x80
>
> 0 42249 free:entry Ptr=0x86d78f0
>
>
>
>
> On 7/2/08 10:14 AM, "Barry Warsaw" <barry at 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 at stanford.edu
Phone: (650) 724-7485
More information about the Mailman-Users
mailing list