Bug 651796 - [abrt] epiphany-1:2.30.5-1.fc14: FixedVMPoolAllocator: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Summary: [abrt] epiphany-1:2.30.5-1.fc14: FixedVMPoolAllocator: Process /usr/bin/epiph...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ace9ed700a06bf81de9661b2d47...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-10 10:10 UTC by romain
Modified: 2012-02-15 09:32 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-15 09:32:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (9.66 KB, text/plain)
2010-11-10 10:10 UTC, romain
no flags Details

Description romain 2010-11-10 10:10:52 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: epiphany
component: epiphany
crash_function: FixedVMPoolAllocator
executable: /usr/bin/epiphany
kernel: 2.6.35.6-48.fc14.x86_64
package: epiphany-1:2.30.5-1.fc14
rating: 4
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289381780
uid: 500

How to reproduce
-----
1. Launch epiphany from GNOME menu
2. It crashes

Comment 1 romain 2010-11-10 10:10:54 UTC
Created attachment 459389 [details]
File: backtrace

Comment 2 Mathieu Bridon 2010-11-14 10:17:54 UTC
Package: epiphany-1:2.30.5-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Click on a link somewhere (xchat, gnome-terminal, evolution,...)
2. Epiphany opens
3. Epiphany crashes before even displaying the web page

This issue is pretty weird. When I open Epiphany for the first time after I have started my session, it works fine. At some point though, it will crash while I'm using it.

After that first crash, Epiphany crashes right when it starts, no matter if it opened automatically when I clicked on a link in another application or if I just ran epiphany.

So it's a 100% reproducer after that initial crash, but it can work flawlessly for a certain amount of time as long as it never crashed (usually the first crash comes after a few hours in my session).

Comment 3 Roumano 2010-11-20 01:38:03 UTC
Package: epiphany-1:2.30.5-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. open the soft
2.
3.

Comment 4 Pete Zaitcev 2010-11-21 02:51:38 UTC
See also bug 648319.

Comment 5 Kevin Fenzi 2010-11-21 04:19:03 UTC
'rpm -q webkitgtk' please from all the folks who see this?

Comment 6 Roumano 2010-11-21 09:01:52 UTC
webkitgtk-1.3.4-3.fc14.1.x86_64

Comment 7 Mathieu Bridon 2010-11-21 11:45:43 UTC
webkitgtk-1.3.4-3.fc14.1.x86_64

Comment 8 Kevin Fenzi 2010-11-21 17:03:15 UTC
yum --enablerepo=updates-testing update webkitgtk

and try again? 

There was a crash with the default fedoraproject.org page with 1.3.4-3. ;(

Comment 9 Mathieu Bridon 2010-11-21 18:13:12 UTC
(In reply to comment #8)
> yum --enablerepo=updates-testing update webkitgtk
> 
> and try again? 
> 
> There was a crash with the default fedoraproject.org page with 1.3.4-3. ;(

You mean http://fedoraproject.org/ ?

I can view it fine with 1.3.4-3.

But as I said in my comment, the crash is hard to reproduce: it's only a 100% reproducer after it first crashed once, which doesn't seem to happen so often. :-/

Comment 10 Kevin Fenzi 2010-11-21 19:17:35 UTC
Odd, in bug 643300 it seemed like it affected all webkit based browsers. ;(

Comment 11 Roumano 2010-11-21 20:37:50 UTC
All webkit for me as banshee with empty configuration file crash ....
But if i remove a lot of plugin on banshee don't crash ...

Comment 12 Roumano 2010-11-22 07:42:17 UTC
Package: epiphany-1:2.30.5-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Open ephiphany (restore tabs)
2.
3.

Comment 13 Roumano 2010-11-22 07:43:58 UTC
Ephiphany still crashing with this version ( yum --enablerepo=updates-testing update webkitgtk == 1.3.6-1.fc14.x86_64) as you can see with my Comment # 12
It restoring my tabs so i don't remember exactaly what it try to open as page ...

Comment 14 Kevin Fenzi 2010-11-23 21:25:57 UTC
I see the orig crash report has: 

Timeout exceeded: 60 second, killing gdb

Can one of you folks who sees the crash gather a full stacktrace from it and add it here?

Comment 15 Roumano 2010-11-23 22:10:49 UTC
Hi,please see bug 656512 for stacktrace --> 
https://bugzilla.redhat.com/attachment.cgi?id=462463

Comment 16 Martin Stransky 2012-02-15 09:32:11 UTC
We're using mozilla crash reporter tool which reports crashes directly to mozilla crash database now, ABRT is no longer used for mozilla packages.

This is an automated bug change. If you can reproduce the crash reliably (you have testcase, page where it crashes or so), please reopen this bug and assign it directly to me.

Thanks.


Note You need to log in before you can comment on or make changes to this bug.