[apport] oops crashed with SIGSEGV in strlen()

Bug #104897 reported by Salva Ferrer
4
Affects Status Importance Assigned to Milestone
oops (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: oops

Using Feisty Fawn in AMD64, updated yesterday.

oops 1.5.23.cvs-4.

I use oops as a local cache to speed my internet connection. oops is used by all applications browsing internet with an HTTP_PROXY env variable pointing to localhost:8123.

oops crashes after sessions of heavy browsing (konqueror with 10s tabs opened) or simply after some hours after startup. There are processes in background that may be using the proxy though.

I am installing the debug version to catch the next crash (should happen in one day or so)

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Apr 9 00:28:11 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/sbin/oops
Package: oops 1.5.23.cvs-4
PackageArchitecture: amd64
ProcCmdline: /usr/sbin/oops -xACDFHINS -c/etc/oops/oops.cfg -d
ProcCwd: /
ProcEnviron:
 LANGUAGE=es_ES:es:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: oops
StacktraceTop:
 strlen () from /lib/libc.so.6
 err () from /usr/lib/oops/err.so
 say_bad_request ()
 ?? ()
 fill_mem_obj ()
Uname: Linux azrael 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux
UserGroups:

Revision history for this message
Salva Ferrer (salva-ferrer) wrote :
Revision history for this message
Salva Ferrer (salva-ferrer) wrote :

I reproduced the crash and it always appears after heavy browsing, Definitelly it looks like a mem leak.

I must admit that it is the first time I use gdb or valgrind I followed the instructions here https://wiki.ubuntu.com/DebuggingProgramCrash

I am attaching gdb traces of the crash; I am not very sure about these because oops crashed as soon as gdb attached to the running oops; and valgrind traces of a crash (oops crased after opening 30 tabs in konqueror)

Revision history for this message
Salva Ferrer (salva-ferrer) wrote :
Revision history for this message
Mario Splivalo (mariosplivalo) wrote :

I can confirm this bug, in a way, at least. I'm using Ubuntu 7.04 on i386, and oops dies usualy every 20 hours. When I run it from terminal without -d option it dies with 'segmentation fault', as described above.

I also noticed that I can cause SIGSEGV by just resizing the terminal I run oops from.

I've been using oops on Ubuntu 6.06 with no problems at all.

Revision history for this message
Tony (tonyj-cooldark) wrote :

Can confirm this with Ubuntu Server Edition 7.04 running oops 1.5.23 under i386.

Crashes frequently for me. Server previously ran an earlier version of Debian and was stable.

Changed in oops:
importance: Undecided → Medium
Revision history for this message
Daniel T Chen (crimsun) wrote :

No longer ships in Ubuntu

Changed in oops:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.