Bug 551924 - [abrt] crash detected in firefox-3.5.6-1.fc12
Summary: [abrt] crash detected in firefox-3.5.6-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 548942
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:2678926db84649800fdcac71b25...
: 551925 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-03 04:29 UTC by Casey Jao
Modified: 2010-01-03 05:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-03 05:25:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.50 KB, text/plain)
2010-01-03 04:29 UTC, Casey Jao
no flags Details

Description Casey Jao 2010-01-03 04:29:09 UTC
abrt 1.0.0 detected a crash.

How to reproduce: Firefox often seg faults when I close it.
Comment: I have many entries like this in my ABRT queue. A new entry is generated every few times I close firefox.
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5.6/firefox
component: firefox
executable: /usr/lib64/firefox-3.5.6/firefox
kernel: 2.6.31.9-174.fc12.x86_64
package: firefox-3.5.6-1.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Casey Jao 2010-01-03 04:29:11 UTC
Created attachment 381350 [details]
File: backtrace

Comment 2 Chris Campbell 2010-01-03 04:58:20 UTC
#2  <signal handler called>
No symbol table info available.
#3  0x0000003958823b88 in IA__g_type_check_instance (
    type_instance=<value optimized out>) at gtype.c:3806
        node = 0xb801003a41000038
#4  0x0000003958822eab in IA__g_signal_handlers_disconnect_matched (
    instance=0x7f3513cfae40, mask=24, signal_id=0, detail=0, closure=0x0, 
    func=<value optimized out>, data=<value optimized out>) at gsignal.c:2667
        n_handlers = 0
        __PRETTY_FUNCTION__ = "IA__g_signal_handlers_disconnect_matched"
#5  0x00007f351a2fcec3 in update_client_widget (
    context_xim=<value optimized out>) at gtkimcontextxim.c:1641
        new_client_widget = 0x0
#6  set_ic_client_window (context_xim=<value optimized out>)
    at gtkimcontextxim.c:654
No locals.
#7  0x00007f351a2fcf5b in xim_info_display_closed (display=0x7f3529da3190, 
    is_error=<value optimized out>, info=0x7f351c8c1890)
    at gtkimcontextxim.c:402
        ics = 0x7f350ca4f420
        tmp_list = 0x7f350ca4f420
#8  0x000000395880ba8e in IA__g_closure_invoke (closure=0x7f3529c13b50, 
    return_value=0x0, n_param_values=2, param_values=0x7f34f342d040, 
    invocation_hint=0x7ffff8bc8c80) at gclosure.c:767
        marshal = <value optimized out>
        marshal_data = <value optimized out>
        in_marshal = <value optimized out>
        __PRETTY_FUNCTION__ = "IA__g_closure_invoke"
#9  0x0000003958820ec3 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 = 0x7f3529c13b20
        accumulator = 0x0
        emission = {next = 0x0, instance = 0x7f3529da3190, ihint = {
            signal_id = 3, detail = 0, run_type = G_SIGNAL_RUN_FIRST}, 
          state = EMISSION_RUN, chain_type = 4}
        class_closure = 0x7f3529d81840
        handler_list = 0x7f351c92b430
        return_accu = 0x0
        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>

Comment 3 Chris Campbell 2010-01-03 05:23:26 UTC
*** Bug 551925 has been marked as a duplicate of this bug. ***

Comment 4 Chris Campbell 2010-01-03 05:25:53 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 548942 ***


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