[issue4732] Object allocation stress leads to segfault on RHEL

2009-02-05 Thread Farshad Khoshkhui
Farshad Khoshkhui added the comment: Sorry wrong issue number. The correct one is #4358 ___ Python tracker <http://bugs.python.org/issue4732> ___ ___ Python-bugs-list m

[issue4732] Object allocation stress leads to segfault on RHEL

2009-02-05 Thread Farshad Khoshkhui
Farshad Khoshkhui added the comment: This happens for me on several debian and ubuntu machines with python 2.5 as well as 2.6 as I reported in #571885. I'll try your script and linking with tcmalloc and get back with results. -- nosy: +fa

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Farshad Khoshkhui
Farshad Khoshkhui <[EMAIL PROTECTED]> added the comment: No, there isn't any custom made C extension, nor I'm using ctypes. (It was a mistake selecting ctypes). The application is a web service with postgresql backend, so it heavily uses pyexpat and pygresql in a threaded en

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Farshad Khoshkhui
Farshad Khoshkhui <[EMAIL PROTECTED]> added the comment: Another Backtrace. I have three other core dumps with exact same backtrace on two different machines. Added file: http://bugs.python.org/file12064/backtrace2 ___ Python tracker <[EMAIL

[issue4358] Segfault in stringobject.c

2008-11-19 Thread Farshad Khoshkhui
New submission from Farshad Khoshkhui <[EMAIL PROTECTED]>: I'm encountering random segfaults on multiple machines. By examining core dumps, it's all happening in stringobject.c (_PyString_Resize or string_join). By using pyframev I figured out it's always happening insi