Bug 651796
| Summary: | [abrt] epiphany-1:2.30.5-1.fc14: FixedVMPoolAllocator: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | romain | ||||
| Component: | epiphany | Assignee: | Gecko Maintainer <gecko-bugs-nobody> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 14 | CC: | bochecha, gecko-bugs-nobody, kevin, rob.townley, roumano, zaitcev | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:ace9ed700a06bf81de9661b2d47297337d2f3f5c | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-02-15 09:32:11 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
romain
2010-11-10 10:10:52 UTC
Created attachment 459389 [details]
File: backtrace
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). 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. See also bug 648319. 'rpm -q webkitgtk' please from all the folks who see this? webkitgtk-1.3.4-3.fc14.1.x86_64 webkitgtk-1.3.4-3.fc14.1.x86_64 yum --enablerepo=updates-testing update webkitgtk and try again? There was a crash with the default fedoraproject.org page with 1.3.4-3. ;( (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. :-/ Odd, in bug 643300 it seemed like it affected all webkit based browsers. ;( All webkit for me as banshee with empty configuration file crash .... But if i remove a lot of plugin on banshee don't crash ... 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. 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 ... 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? Hi,please see bug 656512 for stacktrace --> https://bugzilla.redhat.com/attachment.cgi?id=462463 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. |