gwibber crashed with SIGSEGV

[DKcross]

Binary package hint: gwibber

crashed

ProblemType: Crash
Architecture: i386
CheckboxSubmission: c658f73846a859405903dbcfa12a62da
CheckboxSystem: ed86e29ffba809c116a39e33fa9fc45c
Date: Mon Sep 21 13:50:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.0.0~bzr436-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=es_SV.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
 Segfault happened at: 0x4f0605f: mov (%edi),%eax
 PC (0x04f0605f) ok
 source "(%edi)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
Title: gwibber crashed with SIGSEGV
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:~JSArray (this=0xb51db5c0) at ../JavaScriptCore/wtf/HashTable.h:875
JSC::Heap::sweep<(JSC::HeapType)0> (this=warning: (Internal error: pc 0x4f8b190 in read in psymtab, but not in symtab.)
JSC::Heap::collect (this=0xb6161dac)
WebCore::GCController::gcTimerFired (this=0xb56a73c0)
WebCore::Timer<WebCore::GCController>::fired (

[Victor Vargas (kamus)]

Can you try to reproduce this issue in latest version of gwibber? Thanks!

[Foppe Hemminga (foppe)]

This bug seems to be related to Bug #345704 in gwibber 0.8 / 0.9.
Alexander Sack wrote as comment on those: "pushing a bunch of ubuntu gwibber crashes upstream. If gwibber devs want us to just close them instead let me know (through identi.ca ;)?"

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".