Bug 650567

Summary: [abrt] gwibber-1:2.33.0-12.894bzr.fc14: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Amir Hedayaty <hedayaty>
Component: gwibberAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: tcallawa, zaitcev
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5e552b64ffd0a018647de2c508994dca29c81347
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-01 04:02:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Amir Hedayaty 2010-11-07 03:57:16 UTC 
abrt version: 1.1.13
architecture: x86_64
cmdline: /usr/bin/python /usr/bin/gwibber-accounts
component: gwibber
executable: /usr/bin/python
kernel: 2.6.35.6-48.fc14.x86_64
package: gwibber-1:2.33.0-12.894bzr.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289101874
uid: 500

backtrace
-----
warning: core file may not match specified executable file.
[New Thread 27993]
[New Thread 27998]
[New Thread 27999]
[New Thread 28000]
Core was generated by `/usr/bin/python /usr/bin/gwibber-accounts'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000030052597c3 in FixedVMPoolAllocator (this=<value optimized out>) at JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:308
308	JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp: No such file or directory.

Timeout exceeded: 60 second, killing gdb
Debuginfo absent: 4257771e62117a262b24534d02815175ef7f4164

How to reproduce
-----
1. Try to create and acount (like twitter)
2. It will not ask for username, just authorize!
3. IT WILL CRASH
Comment 1 Amir Hedayaty 2010-11-07 03:57:18 UTC 
Created attachment 458415 [details]
File: backtrace
Comment 2 Pete Zaitcev 2010-11-18 15:26:35 UTC 
So, what package is missing? A piece of WebKit of some kind, but what?
Comment 3 Tom "spot" Callaway 2010-11-18 15:33:29 UTC 
No idea. I can't reproduce this one, so I'm not sure how to start debugging it.
Comment 4 Pete Zaitcev 2010-11-18 17:10:39 UTC 
BTW, I just received a GNOME notification. Indeed, every crashed gwibber
leaves behind a little zombie:

[zaitcev@lembas hail]$ ps auxw| grep -i gwib
zaitcev   3188  0.1  1.6 862660 31796 ?        SLl  08:08   0:08 /usr/bin/python /usr/bin/gwibber-service
zaitcev   3194  0.0  1.2 509848 25276 ?        S    08:08   0:01 /usr/bin/python /usr/bin/gwibber-service
zaitcev   3195  0.0  1.2 509560 24864 ?        S    08:08   0:01 /usr/bin/python /usr/bin/gwibber-service
[zaitcev@lembas hail]$ 

I can understand it not being removed after crash, but why are there
three of them?
Comment 5 Pete Zaitcev 2010-11-18 17:20:50 UTC 
Never mind, abrt misled me. I am going to keep bug 654677 unduped for now,
it's a normal crash and not a missing package.
Comment 6 Pete Zaitcev 2010-12-01 04:02:40 UTC 
I'm pretty sure this is a duplicate of bug 648319, closing as such.

*** This bug has been marked as a duplicate of bug 648319 ***