On Fri, 2009-09-11 at 04:13 -0700, rufus nayagam wrote: > Often we get the following error. > > b79d5000-b79d7000 rw-p b79d*** glibc detected *** python: double free > or corruption (fasttop): 0x084dcaa8 *** > > We understand its a memory related error... And we give... > > export MALLOC_CHECK_=0 as a temporary solution.. > > What will be the permanent solution for this and any information why > this is happening please advise >
That is not a solution; it merely hides the problem. You might as well keep it outputting the warning to remind you that you do have a problem.. The easiest way is to run with MALLOC_CHECK_=3, which will result in both an error message, and the program will abort at exactly that point. This should give you a core dump, which will indicate in which code you are having the problem, and you can work from there to fix/replace the broken code. Cheers Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
