Bug 528859 - [abrt] crash detected in firefox-3.5.3-1.fc12
Summary: [abrt] crash detected in firefox-3.5.3-1.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nspr
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kai Engert (:kaie) (inactive account)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5415619cb3b48d799fa61802d3b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-14 05:37 UTC by Renich Bon Ciric
Modified: 2018-04-11 07:18 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-23 20:25:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (47.11 KB, text/plain)
2009-10-14 05:37 UTC, Renich Bon Ciric 		no flags Details
View All

Description Renich Bon Ciric 2009-10-14 05:37:06 UTC 
abrt detected a crash.


How to reproduce
-----
1. Try and add a contact at gmail's contact section


Comment
-----
I can't reproduce this... I hope the traceback helps!

Additional information
======


Attached files
----
backtrace

cmdline
-----
/usr/lib64/firefox-3.5.3/firefox 


component
-----
firefox


executable
-----
/usr/lib64/firefox-3.5.3/firefox


kernel
-----
2.6.31.1-56.fc12.x86_64


package
-----
firefox-3.5.3-1.fc12


reason
-----
Process was terminated by signal 11
Comment 1 Renich Bon Ciric 2009-10-14 05:37:10 UTC 
Created attachment 364692 [details]
File: backtrace
Comment 2 Matěj Cepl 2009-10-14 14:06:08 UTC 
Looks like crap in nspr, reassigning.
Comment 3 Bug Zapper 2009-11-16 13:38:47 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 Kai Engert (:kaie) (inactive account) 2010-03-23 20:25:39 UTC 
Sorry, there isn't any helpful data in the stack, because there wasn't debuginfo for the xulrunner package installed.
Note You need to log in before you can comment on or make changes to this bug.