Bug 691116 - [abrt] firefox-3.6.15-1.fc14: nsProfileLock::Lock: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.15-1.fc14: nsProfileLock::Lock: Process /usr/lib/firefox-3...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:22e8ec58eb325c970ac25108670...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-26 20:21 UTC by Rob
Modified: 2011-12-07 13:16 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (42.49 KB, text/plain)
2011-03-26 20:21 UTC, Rob 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Rob 2011-03-26 20:21:20 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 43510 bytes
cmdline: /usr/lib/firefox-3.6/firefox --sm-config-prefix /firefox-7Cqx2k/ --sm-client-id 10d0e85cce68d22a69129968890423926600000021370070 --screen 0
comment: No idea.
component: firefox
Attached file: coredump, 295784448 bytes
crash_function: nsProfileLock::Lock
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.35.11-83.fc14.i686.PAE
package: firefox-3.6.15-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300683334
uid: 500

How to reproduce
-----
1. Eclipse would not properly debug. Kept getting a debugInfo.c error.
2. The following day (today) I was using FireFox to post on Facebook and it crashed.
3.
Comment 1 Rob 2011-03-26 20:21:23 UTC 
Created attachment 487950 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:16:04 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.