Bug 625203 - [abrt] firefox-3.6.7-1.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
Summary: [abrt] firefox-3.6.7-1.fc13: Process /usr/lib64/firefox-3.6/firefox was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 543165
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bcaab8bbb3e49ac46fa2dbf48c3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-18 21:03 UTC by Jay
Modified: 2018-04-11 11:51 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-23 15:17:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (31.69 KB, text/plain)
2010-08-18 21:03 UTC, Jay
no flags Details

Description Jay 2010-08-18 21:03:34 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox
comment: Java also crashed at the same time and WebCT is programmed mainly in Java.  I am unable to send the Java error even after trying the debug-install.
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: firefox-3.6.7-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: I think I was logging out of WebCT (something used in universities).
time: 1282148260
uid: 500

Comment 1 Jay 2010-08-18 21:03:37 UTC
Created an attachment (id=439507)
File: backtrace

Comment 2 Daniel Demus 2010-08-19 17:12:16 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
I had left the machine and it was sitting idle.

Comment 3 Jérôme Benoit 2010-08-24 20:55:19 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Doing a search on the search toolbar
2.
3.

Comment 4 freonmonkey 2010-09-04 20:13:33 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Open multiple tabs and windows.
2. Close windows and tabs sequentially by hand.
3. Close Firefox when only one tab is left; Firefox crashes on shutdown.

Comment
-----
This doesn't seem to come from having many tabs; I regularly use plenty of tabs without issue.
I suspect it has more to do with having multiple windows. I rarely have need to do so, but this bug comes up just as rarely.
I tend to use keyboard shortcuts and mouse gestures rather than menus.

Comment 5 Egon Kastelijn 2010-09-05 21:09:52 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
I closed firefox.

Comment 6 Nuno Anjos 2010-09-06 11:13:22 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
changing network.

Comment 7 Matthew Saltzman 2010-09-06 14:23:28 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Crash occurred while trying to restore after machine lockup.  On restarting, I got the window that 
indicates trouble restoring tabs,  When I selected to opion to restore the tabs anyway, the crash occurred.
On the next startup, all tabs were lost.

Comment 8 Svyatoslav Evzhenkov 2010-09-07 11:19:49 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. I was working with Google Docs
2. pressed ALT+TAB
3. ff crashed

in ff:
- running flash player
- running google apps


Comment
-----
Sorry, I've got no idea how to reproduce the bug. It happens every now and then, but I couldn't reproduce it

Comment 9 ksp1717 2010-09-09 01:26:51 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. run a flash video in firefox.
2. close firefox and after the video finished running.
3.

Comment 10 Eric Blake 2010-09-11 15:27:28 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
closing down firefox

Comment 11 freonmonkey 2010-09-11 18:10:33 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Closed Firefox after resuming the system from RAM sleep.


Comment
-----
I closed Firefox after resuming from standby.

Comment 12 Svyatoslav Evzhenkov 2010-09-13 06:53:32 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. closed ff and it crashed
2. Had Google docs running in ff only (4 tabs). No flash objects were running 
3. I do not thing reprodction possible

Comment 13 Răzvan Sandu 2010-09-15 04:37:23 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----

Comment 14 Rob 2010-09-19 20:07:37 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Closed firefox
2. ABRT popped up saying firefox had crashed
3.

Comment 15 Robin R. Price II 2010-09-21 21:55:30 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.  Opened firefox
2.  Opened pdf file
3.


Comment
-----
You rock

Comment 16 Robin R. Price II 2010-09-22 18:59:10 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.  Opened firefox
2.  Opened pdf file
3.


Comment
-----
This is a test

Comment 17 Ankur Sinha (FranciscoD) 2010-09-22 19:33:44 UTC
Package: firefox-3.6.7-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. closed FF
2.
3.

Comment 18 Matěj Cepl 2010-09-23 15:17:04 UTC

*** This bug has been marked as a duplicate of bug 543165 ***


Note You need to log in before you can comment on or make changes to this bug.