empathy crashed with SIGSEGV in WTF::OSAllocator::reserveAndCommit()

[pschonmann]

Binary package hint: empathy

Crashed when conversation window is opened.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.32.2-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Tue Jan 25 10:07:41 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=en_AG.utf8
 LANGUAGE=en
 LANG=cs_CZ.utf8
SegvAnalysis:
 Segfault happened at: 0x7f3892edf5c5 <WTF::OSAllocator::reserveAndCommit(size_t, WTF::OSAllocator::Usage, bool, bool)+69>: movl $0x0,(%rdx)
 PC (0x7f3892edf5c5) ok
 source "$0x0" ok
 destination "(%rdx)" (0xbbadbeef) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 WTF::OSAllocator::reserveAndCommit (bytes=<value optimized out>, usage=<value optimized out>, writable=<value optimized out>, executable=<value optimized out>) at ../Source/JavaScriptCore/wtf/OSAllocatorPosix.cpp:85
 reserve (this=<value optimized out>) at ../Source/JavaScriptCore/wtf/PageReservation.h:101
 FixedVMPoolAllocator (this=<value optimized out>) at ../Source/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:281
 JSC::ExecutableAllocator::isValid (this=<value optimized out>) at ../Source/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:440
 ExecutableAllocator (this=0x7f3882701000, globalDataType=JSC::JSGlobalData::Default, threadStackType=JSC::ThreadStackTypeLarge) at ../Source/JavaScriptCore/jit/ExecutableAllocator.h:178
Title: empathy crashed with SIGSEGV in WTF::OSAllocator::reserveAndCommit()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 WTF::OSAllocator::reserveAndCommit (
 ?? ()
 ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libpixman-1-0-dbg: installed version 0.21.4-1~xorgedgers, latest version: 0.18.4-1build1
libdrm-intel1-dbg: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1
libxcb-shm0: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libdrm-nouveau1: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1
libdrm2-dbg: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1
libdrm-intel1: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1
libnspr4-0d-dbg: installed version 4.8.7-0ubuntu1, latest version: 4.8.6-0ubuntu1
libxcb-render0-dbg: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libdrm-nouveau1-dbg: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1
libxcb-render0: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libxcb1-dbg: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libpixman-1-0: installed version 0.21.4-1~xorgedgers, latest version: 0.18.4-1build1
libdrm-radeon1-dbg: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1
libxcb-shm0-dbg: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libdrm2: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1
libxcb1: installed version 1.7-0ubuntu0sarvatt2, latest version: 1.6-1
libnss3-1d-dbg: installed version 3.12.9~b2-0ubuntu1, latest version: 3.12.8-0ubuntu0.10.10.1
libdrm-radeon1: installed version 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt, latest version: 2.4.22-2ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[pschonmann (pschonmann)]

Please look at this ticket. Im unable to communicate with empathy ! Its blocker.

[Brian Curtis (bcurtiswx)]

As the previous message has stated, please try a sudo apt-get update; sudo apt-get upgrade/dist-upgrade or sudo apt-get install --reinstall empathy to make sure you have the most current version of the software. Right now I can not cause it to crash when the conversation window is opened.

[pschonmann (pschonmann)]

Hi Brian,
I tried everything what you described, but unsucessfull. Im able to provide empathy debug logs, but i dont want to show sensitive informations.
Maybe valgrind log should be usefull if you want it.

[Brian Curtis (bcurtiswx)]

OK, please provide a backtrace
In a terminal:
gdb empathy

In gdb:
run
(when crash happens) backtrace

Save that and post it here please.

[Brian Curtis (bcurtiswx)]

also make sure that you have empathy-dbg installed

[pschonmann (pschonmann)]

Version: 2.32.2-0ubuntu7 installed, problem still persist

[Brian Curtis (bcurtiswx)]

This is a webkit issue and I am marking it as such. From this point it's up to the webkit people since the crash was caused in webkit.

[pschonmann (pschonmann)]

echo 1 > /proc/sys/vm/overcommit_memory

works for me as workaround