Bug 767471 - [abrt] xulrunner-1.9.2.24-1.fc14: XChangeProperty: Process /usr/lib64/xulrunner-1.9.2/plugin-container was killed by signal 11 (SIGSEGV)
Summary: [abrt] xulrunner-1.9.2.24-1.fc14: XChangeProperty: Process /usr/lib64/xulrunn...
Keywords:
Status: CLOSED WORKSFORME
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:0b08f982db8b3f6e7a70620a7a0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-14 06:56 UTC by Daniel S Spicer
Modified: 2012-02-15 09:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-15 09:26:03 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (61.32 KB, text/plain)
2011-12-14 06:56 UTC, Daniel S Spicer 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Daniel S Spicer 2011-12-14 06:56:48 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 62789 bytes
cmdline: /usr/lib64/xulrunner-1.9.2/plugin-container /usr/lib64/flash-plugin/libflashplayer.so 2678 plugin true
component: xulrunner
Attached file: coredump, 188227584 bytes
crash_function: XChangeProperty
executable: /usr/lib64/xulrunner-1.9.2/plugin-container
kernel: 2.6.35.14-106.fc14.x86_64
package: xulrunner-1.9.2.24-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: 1323827654
uid: 7001

How to reproduce
-----
1.using Firefox 3.6.24
2.
3.
Comment 1 Daniel S Spicer 2011-12-14 06:56:52 UTC 
Created attachment 546588 [details]
File: backtrace
Comment 2 Martin Stransky 2012-02-15 09:26:03 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.