gwibber crashed with SIGSEGV

Bug #442693 reported by Matthew Pirocchi
112
This bug affects 13 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gwibber

I installed Gwibber, started it, and added my twitter account. Gwibber froze, then crashed.

ProblemType: Crash
Architecture: i386
Date: Sun Oct 4 20:10:20 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.0.0~bzr449-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x3efe4c7: mov (%eax),%edi
 PC (0x03efe4c7) ok
 source "(%eax)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%edi" 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-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:WTF::HashTable<WebCore::AtomicString, std::pair<WebCore::AtomicString, WebCore::String>, WTF::PairFirstExtractor<std::pair<WebCore::AtomicString, WebCore::String> >, WebCore::CaseFoldingHash, WTF::PairHashTraits<WTF::HashTraits<WebCore::AtomicString>, WTF::HashTraits<WebCore::String> >, WTF::HashTraits<WebCore::AtomicString> >::deallocateTable (table=0xb537f000, size=64)
~ResourceLoader (this=0xb537f400)
~SubresourceLoader (this=0xb537f400)
WebCore::SubresourceLoader::didFinishLoading (
WebCore::ResourceLoader::didFinishLoading (this=0xb537f400)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

I tried to reproduce this issue in gwibber (2.0.0 bzr478) and works fine for me, Can you try to reproduce this issue in latest version of gwibber? Thanks!

Changed in gwibber (Ubuntu):
status: New → Incomplete
Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

I'm unable to reproduce this bug. I'll follow-up if it happens again.

Revision history for this message
Victor Vargas (kamus) wrote :

Well, according to your last message this issue was fixed. Thanks!

Changed in gwibber (Ubuntu):
status: Incomplete → Fix Released
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.