Bug 694825 - [abrt] xulrunner-1.9.2.16-1.fc14: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
Summary: [abrt] xulrunner-1.9.2.16-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:458b59098d790b6e71864c3d25d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-08 14:26 UTC by Dave
Modified: 2011-12-07 13:28 UTC (History)
5 users (show)

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

Attachments (Terms of Use)
File: backtrace (37.07 KB, text/plain)
2011-04-08 14:26 UTC, Dave 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Dave 2011-04-08 14:26:50 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 37955 bytes
cmdline: /usr/lib64/xulrunner-1.9.2/plugin-container /usr/lib64/flash-plugin/libflashplayer.so 22984 plugin false
component: xulrunner
Attached file: coredump, 172859392 bytes
crash_function: base::BaseTimer_Helper::OrphanDelayedTask
executable: /usr/lib64/xulrunner-1.9.2/plugin-container
kernel: 2.6.35.10-74.fc14.x86_64
package: xulrunner-1.9.2.16-1.fc14
rating: 3
reason: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302272638
uid: 500

How to reproduce
-----
1. Crashed while exiting. Had consumed too much memory and was very sluggish, so tried to restart and apparently it crashed.
2.
3.
Comment 1 Dave 2011-04-08 14:26:52 UTC 
Created attachment 490809 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:28:40 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.