> All I can suggest at this point are:
>
> 1. Disable the background email thread and see if the problem still occurs.
>
> 2. Force application to run in main interpreter by setting:
>
> WSGIApplicationGroup %{GLOBAL}
>
> This will eliminate possibility that problems are caused by a third
> party C extension module which isn't implemented correctly so as to
> work in secondary sub interpreters.
>
> 3. Try and attach gdb, if available, to running daemon process and see
> if you can catch traceback for what causes process to crash. See:
>
> http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Debugging_C...
Thanks for these tips so far.
You're writing about external threads... so I started wondering about
django-compress. This app uses external applications eg. yui
compressor or csstidy to compress all js and css files into one, big
resource file (one for js and one for css). It does merging during
startup of django processes but, AFAIK, only if there are any changes
in js or css files, so this shouldn't be an issue when recent
segmentation fault happened in my Apache, as there were no changes,
but maybe it is somehow connected. I don't know the internals of
django-compress too much.
--
Maciej Wisniowski
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
