pinger crashed with SIGSEGV in malloc_consolidate()

[Barry Warsaw]

Saw the crash this morning, no obvious cause.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: squid3 3.3.8-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Tue Aug 20 07:35:24 2013
ExecutablePath: /usr/lib/squid3/pinger
InstallationDate: Installed on 2011-07-12 (769 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
MarkForUpload: True
ProcCmdline: (pinger)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fdaac903b7d <malloc_consolidate+125>: cmp 0x18(%rax),%r12
 PC (0x7fdaac903b7d) ok
 source "0x18(%rax)" (0x732bdff0098) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: squid3
StacktraceTop:
 malloc_consolidate (av=av@entry=0x7fdaacc44740 <main_arena>) at malloc.c:4081
 _int_free (av=0x7fdaacc44740 <main_arena>, p=0x7fdaae6faf90, have_lock=0) at malloc.c:3973
 std::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >::~basic_ostringstream() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? ()
 ?? ()
Title: pinger crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to saucy on 2011-12-23 (605 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 malloc_consolidate (av=av@entry=0x7fdaacc44740 <main_arena>) at malloc.c:4081
 _int_free (av=0x7fdaacc44740 <main_arena>, p=0x7fdaae6faf90, have_lock=0) at malloc.c:3973
 _M_dispose (__a=..., this=<optimized out>) at /build/buildd/gcc-4.8-4.8.1/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.h:249
 ~basic_string (this=0x7fdaae6fae80, __in_chrg=<optimized out>) at /build/buildd/gcc-4.8-4.8.1/build/x86_64-linux-gnu/libstdc++-v3/include/bits/basic_string.h:539
 ~basic_stringbuf (this=0x7fdaae6fae38, __in_chrg=<optimized out>) at /build/buildd/gcc-4.8-4.8.1/build/x86_64-linux-gnu/libstdc++-v3/include/sstream:64

[Launchpad Janitor (janitor)]

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

[Omid Kosari (omidkosari)]

I think the importance of this bug should change to HIGH .

Any workaround ?

[Omid Kosari (omidkosari)]

Forgot to say i'm using stable version of ubuntu 13.10

[Omid Kosari (omidkosari)]

Even same problem appears when http://packages.ubuntu.com/saucy/squid3 installed on Ubuntu 12.10

[derek dickerson (dickerson-derek)]

Any solution yet or workaround This doesn't do this with Mint Linux

This issue is confirmed with Ubuntu 14.04 Trusty.

[Frank Brown (frankjbrown)]

Having same problem with squid3 3.3.8-1ubuntu6, running Ubuntu 14.04 within a VirtualBox Vm. Any solution yet?

[Eric Detheridge (ericdetheridge)]

Got a similar crash in 14.04 while using Synaptic to perform an upgrade. Have version 0.8.6 of squid-deb-proxy and squid-deb-proxy-client installed.

[Derek Chen-Becker (dchenbecker)]

I see the same crash from time to time as well. Ubuntu 14.04.3, with squid3 3.3.8-1ubuntu6.2.

[Stuart Bishop (stub)]

Ended up here via Bug #1236239 with 16.04 (beta)

[Amos Jeffries (yadi)]

This is fixed in the squid package now available in Xenial.

[Alexander List (alexlist)]

Unfortunately, I still get errors on Xenial:

Apr 26 12:50:35 xx whoopsie[1203]: [12:50:35] Parsing /var/crash/_usr_lib_squid_pinger.0.crash.
Apr 26 12:50:35 xx whoopsie[1203]: [12:50:35] Uploading /var/crash/_usr_lib_squid_pinger.0.crash.
Apr 26 12:50:38 xx whoopsie[1203]: [12:50:38] Sent; server replied with: No error
Apr 26 12:50:38 xx whoopsie[1203]: [12:50:38] Response code: 200
Apr 26 12:50:38 xx whoopsie[1203]: [12:50:38] Reported OOPS ID 6acdb2bc-0b6a-11e6-a507-fa163e8d4bab

pinger assert failure: *** Error in `(pinger)': free(): invalid pointer: 0x0000555b3c501070 ***

$ apt-cache policy squid
squid:
  Installed: 3.5.12-1ubuntu7
  Candidate: 3.5.12-1ubuntu7

[Amos Jeffries (yadi)]

Can you please provide a backtrace from the new crash?

[Richard (rmustakos)]

I have always gotten this, but I get this on an increasingly regular basis. Multiple times a day when I am logged in. If I SSH in I don't get it, but then it makes dev an issue.
I'm running 14.04 LTS

[Richard (rmustakos)]

If you let me know what files would help debug it, i'll upload them.
Thanks