To Alexandre: Thanks for that link. I do not use py-mxDateTime normally so I never installed it on my test machine. Once I did, I started receiving those errors that both Ian and Darrin were reporting with Django 1.0+. py-mxDateTime contains the mxTextTools library that seems to be (at least) one of the factors based on the information in the trouble ticket link that you provided. The funny thing is that when I pkg_delete py-mxDateTime, Django starts working normally again with no dumps.
And just to update everyone else: Since Alexandre pointed out that trouble ticket, I've been trying to back track exactly where the problem seems to occur. From what I can tell, the core dump occurs during the get_response method in /usr/local/lib/python2.5/site-packages/django/core/handlers/base.py. Upon further inspection (by printing the vars), I found that the problem seems to be with the request object that is passed into the get_response method. Also, this seems to only occur when content type of the object is listed as "multipart/form-data", which is probably why certain actions work (like adding users) and others cause the dump (like updating users or adding groups). What I don't understand is why mxTextTools would be causing Django to dump since I couldn't find any indication within the Django code that references mxTextTools. Does anyone know why this would occur? Anyways, back to work... Thanks, Ryan On Sun, May 17, 2009 at 7:56 AM, Ian Darwin <[email protected]> wrote: > Darrin Chandler wrote: >> >> On Sat, May 16, 2009 at 04:05:10PM -0700, Ryan Boggs wrote: >> >>> >>> Hey Darrin, >>> >>> If no one else is interested, I would like to work on it. >>> >>> Where exactly is the crash happening in Admin? >>> >> >> In 1.0 the crash happened trying to save a new user, iirc. For 1.0.2 you >> could save a new user, but further editing and saving would crash. If >> I'm remembering right (which may not be the case) it was actually >> crashing python. >> > > Yes, malloc detects a double free and the whole thing crashes. >
