[searx] - uwsgi-core crashed with SIGSEGV in __libc_fork()

[Thomas Ward]

searx causes this crash. This should probably be filed as a searx bug, and is related to bug 1772749

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: uwsgi-core 2.0.15-11
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
Date: Tue May 22 21:00:27 2018
ExecutablePath: /usr/bin/uwsgi-core
ProcCmdline: /usr/bin/uwsgi --ini /usr/share/uwsgi/conf/default.ini --ini /etc/uwsgi/apps-enabled/searx.ini --daemonize /var/log/uwsgi/app/searx.log
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fd87b84b51f: cmpb $0x48,(%rax)
 PC (0x7fd87b84b51f) ok
 source "$0x48" ok
 destination "(%rax)" (0x7fd87988f500) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: uwsgi
StacktraceTop:
 ?? ()
 __libc_fork () at ../sysdeps/nptl/fork.c:204
 daemonize (logfile=0x55b70f7a1440 "/var/log/uwsgi/app/searx.log") at core/utils.c:137
 uwsgi_setup (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at core/uwsgi.c:2279
 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at core/uwsgi.c:2011
Title: uwsgi-core crashed with SIGSEGV in __libc_fork()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 __libc_fork () at ../sysdeps/nptl/fork.c:204
 daemonize (logfile=0x55b70f7a1440 "/var/log/uwsgi/app/searx.log") at core/utils.c:137
 uwsgi_setup (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at core/uwsgi.c:2279
 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at core/uwsgi.c:2011

[Thomas Ward (teward)]

Related Debian bug upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900068

[Thomas Ward (teward)]

Debian has found the same report in the upstream searx package:

https://github.com/asciimoo/searx/issues/929

However the reported issue *there* is more than a year old, without any action on it.