Bug 569522 - [abrt] crash in firefox-3.5.8-1.fc12: Process /usr/lib64/firefox-3.5.8/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.5.8-1.fc12: Process /usr/lib64/firefox-3.5.8/firefo...
Keywords:
Status: CLOSED DUPLICATE of bug 533029
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ed9121ec722e374a14f934fc046...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-01 16:30 UTC by Jared Smith
Modified: 2011-11-17 08:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-02 19:45:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (64.13 KB, text/plain)
2010-03-01 16:30 UTC, Jared Smith
no flags Details

Description Jared Smith 2010-03-01 16:30:02 UTC
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5.8/firefox
comment: Not sure what caused this bug... I had Firefox open but was not actively using it when it crashed.
component: firefox
executable: /usr/lib64/firefox-3.5.8/firefox
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: firefox-3.5.8-1.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5.8/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Run firefox
2. Have it sit there running while using another application (terminal, in my case)
3. Have it crash :-(

Comment 1 Jared Smith 2010-03-01 16:30:05 UTC
Created attachment 397109 [details]
File: backtrace

Comment 2 Chris Campbell 2010-03-02 19:41:48 UTC
#2  <signal handler called>
No symbol table info available.
#3  0x00007f12677c6310 in ?? ()
No symbol table info available.
#4  0x00000038fd611c7f in marshal_dbus_message_to_g_marshaller (
    closure=<value optimized out>, return_value=0x0, 
    n_param_values=<value optimized out>, param_values=<value optimized out>, 
    invocation_hint=0x7fff528895d0, marshal_data=0x0) at dbus-gproxy.c:1681
        value_array = <value optimized out>
        c_marshaller = <value optimized out>
        proxy = 0x7f124b874da0 [DBusGProxy]
        __PRETTY_FUNCTION__ = "marshal_dbus_message_to_g_marshaller"
#5  0x00000038fa60ba8e in IA__g_closure_invoke (closure=0x7f1249e1b790, 
    return_value=0x0, n_param_values=3, param_values=0x7f1243e43330, 
    invocation_hint=0x7fff528895d0) at gclosure.c:767
        marshal = <value optimized out>
        marshal_data = <value optimized out>
        in_marshal = <value optimized out>
        __PRETTY_FUNCTION__ = "IA__g_closure_invoke"
#6  0x00000038fa620ec3 in signal_emit_unlocked_R (node=<value optimized out>, 
    detail=<value optimized out>, instance=<value optimized out>, 
    emission_return=<value optimized out>, 
    instance_and_params=<value optimized out>) at gsignal.c:3247
        tmp = <value optimized out>
        handler = 0x7f1249e1b9d0
        emission = {next = 0x0, instance = 0x7f124b874da0, ihint = {
            signal_id = 346, detail = 1714, run_type = G_SIGNAL_RUN_FIRST}, 
          state = EMISSION_RUN, chain_type = 4}
        handler_list = 0x7f1249e1b9d0
        accu = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0, 
              v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 
    0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, 
              v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, 
              v_pointer = 0x0}}}
        signal_id = <value optimized out>
        max_sequential_handler_number = <value optimized out>
        return_value_altered = <value optimized out>




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Chris Campbell 2010-03-02 19:45:08 UTC
Thank you for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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


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