Bug 676466 - [abrt] xulrunner-1.9.2.13-5.fc14: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
Summary: [abrt] xulrunner-1.9.2.13-5.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:356e6490f23a059fb4db48e29ac...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-09 23:01 UTC by Allan Engelhardt
Modified: 2011-12-07 13:29 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
File: backtrace (16.72 KB, text/plain)
2011-02-09 23:01 UTC, Allan Engelhardt
no flags Details

Description Allan Engelhardt 2011-02-09 23:01:01 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/xulrunner-1.9.2/plugin-container /home/allane/.mozilla/plugins/libflashplayer.so 6278 plugin
component: xulrunner
executable: /usr/lib64/xulrunner-1.9.2/plugin-container
kernel: 2.6.35.10-74.fc14.x86_64
package: xulrunner-1.9.2.13-5.fc14
rating: 0
reason: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Loading new site after restarting broadband connection on the external 'modem' caused Firefox (and `/usr/lib64/xulrunner-1.9.2/plugin-container /home/allane/.mozilla/plugins/libfl') to crash (so probably related to the Adobe Flash plugin and not a Firefox bug as such?)
time: 1297291837
uid: 500

Comment 1 Allan Engelhardt 2011-02-09 23:01:05 UTC
Created attachment 477923 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:29:20 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.