apache2 crashed with SIGABRT in Py_FatalError()

[Cristian Aravena Romero]

Crash.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apache2-bin 2.4.6-2ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 28 07:46:15 2013
ExecutablePath: /usr/sbin/apache2
InstallationDate: Installed on 2013-07-05 (23 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
MarkForUpload: True
ProcCmdline: /usr/sbin/apache2 -k start
ProcEnviron:
 PATH=(custom, no user)
 LANG=C
Signal: 6
SourcePackage: apache2
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 Py_FatalError () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 PyEval_AcquireThread () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 ?? () from /usr/lib/apache2/modules/mod_wsgi.so
Title: apache2 crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 Py_FatalError () from /tmp/apport_sandbox_zol_9j/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 PyEval_AcquireThread () from /tmp/apport_sandbox_zol_9j/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 wsgi_python_child_cleanup (data=<optimized out>) at mod_wsgi.c:6885
 run_cleanups (cref=<optimized out>) at ../memory/unix/apr_pools.c:2352
 apr_pool_destroy (pool=0x7f894ffad028) at ../memory/unix/apr_pools.c:814

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[martin suc (martin-suc)]

problem as well in ubuntu utopic 14.10

[Robie Basak (racb)]

Can someone post steps to reproduce this, please? With six people affected it's clearly a bug that exists and is valid, but without steps to reproduce it's really difficult for a developer to even make a start on the problem.