Bug 676810 - [abrt] firefox-3.6.13-1.fc14: operator new: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
Summary: [abrt] firefox-3.6.13-1.fc14: operator new: Process /usr/lib64/firefox-3.6/fi...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:094df69bdcb029a0a11066b73b6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-11 11:13 UTC by Markus Schulze
Modified: 2011-12-07 13:17 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (60.77 KB, text/plain)
2011-02-11 11:13 UTC, Markus Schulze 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Markus Schulze 2011-02-11 11:13:47 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale de
component: firefox
crash_function: operator new
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.35.10-74.fc14.x86_64
package: firefox-3.6.13-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. I did nothing special, left 2 browser windows with several tabs open and idle while working with other programms
time: 1297421917
uid: 500
Comment 1 Markus Schulze 2011-02-11 11:13:50 UTC 
Created attachment 478216 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:17:26 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.