Bug 690018 - [abrt] xulrunner-1.9.2.15-1.fc14: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
Summary: [abrt] xulrunner-1.9.2.15-1.fc14: Process /usr/lib64/xulrunner-1.9.2/plugin-c...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xulrunner
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9c0e3dc98eb55469d8ef1bc47c2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-23 02:37 UTC by Jameson
Modified: 2011-12-07 13:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:31:07 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (28.21 KB, text/plain)
2011-03-23 02:37 UTC, Jameson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jameson 2011-03-23 02:37:07 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 28883 bytes
cmdline: /usr/lib64/xulrunner-1.9.2/plugin-container /usr/lib64/mozilla/plugins-wrapped/nswrapper_64_64.libflashplayer.so 3018 plugin false
component: xulrunner
Attached file: coredump, 12709888 bytes
crash_function: mozilla::(anonymous namespace)::child::_geturlnotify
executable: /usr/lib64/xulrunner-1.9.2/plugin-container
kernel: 2.6.35.11-83.fc14.x86_64
package: xulrunner-1.9.2.15-1.fc14
rating: 4
reason: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300833556
uid: 500

How to reproduce
-----
1.  Opened a link from a Google image search in a new tab.
2.  It crashed while the page was loading.
Comment 1 Jameson 2011-03-23 02:37:10 UTC 
Created attachment 486946 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:31:07 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

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