gwibber-bugs team mailing list archive

[Mohamed IKBEL Boulabiar <628092@xxxxxxxxxxxxxxxxxx>]

** Changed in: gwibber (Ubuntu)
       Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/628092

Title:
  gwibber-service crashed with SIGSEGV in JSGarbageCollect()

Status in Gwibber:
  New
Status in “gwibber” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gwibber

I haven't done anything to get it crashed...

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
NonfreeKernelModules: wl
Architecture: i386
CrashCounter: 1
Date: Wed Sep  1 11:47:07 2010
ExecutablePath: /usr/bin/gwibber-service
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x20dd492 <JSGarbageCollect+34>:	mov    0x8(%eax),%eax
 PC (0x020dd492) ok
 source "0x8(%eax)" (0x736f6830) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 JSGarbageCollect () from /usr/lib/libwebkit-1.0.so.2
 ?? ()
 ?? ()
 ?? () from /usr/lib/libproxy.so.0
 px_array_free () from /usr/lib/libproxy.so.0
Title: gwibber-service crashed with SIGSEGV in JSGarbageCollect()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare