Bug 548188 - [abrt] crash in firefox-3.5.6-1.fc12
Summary: [abrt] crash in firefox-3.5.6-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 543165
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:0ef670ef03f0e5d985931375066...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-16 21:04 UTC by Dario Castellarin
Modified: 2010-01-10 19:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-17 16:57:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (18.72 KB, text/plain)
2009-12-16 21:04 UTC, Dario Castellarin
no flags Details

Description Dario Castellarin 2009-12-16 21:04:53 UTC
abrt 1.0.2 detected a crash.

Comment: As usual, use firefox with any flash content, then close it
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.8-169.fc12.x86_64
package: firefox-3.5.6-1.fc12
rating: 3
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Dario Castellarin 2009-12-16 21:04:57 UTC
Created attachment 378848 [details]
File: backtrace

Comment 2 Chris Campbell 2009-12-17 16:56:41 UTC
#2  <signal handler called>
No symbol table info available.
#3  IA__g_type_check_instance (type_instance=0x7f671b803cc0) at gtype.c:3804
        node = <value optimized out>
#4  0x00000030aae22eab in IA__g_signal_handlers_disconnect_matched (
    instance=0x7f671b803cc0, 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  0x00007f67243fcec3 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  0x00007f67243fcf5b in xim_info_display_closed (display=0x7f67348a0190, 
    is_error=<value optimized out>, info=0x7f6727e16fd0)
    at gtkimcontextxim.c:402
        ics = 0x7f671bc1a320
        tmp_list = 0x7f671d4aa2d0
#8  0x00000030aae0ba8e in IA__g_closure_invoke (closure=0x7f67263d2c40, 
    return_value=0x0, n_param_values=2, param_values=0x7f671b737040, 
    invocation_hint=0x7fff5181ee90) 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  0x00000030aae20ec3 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 = 0x7f67263d2c10
        accumulator = 0x0
        emission = {next = 0x0, instance = 0x7f67348a0190, ihint = {
            signal_id = 3, detail = 0, run_type = G_SIGNAL_RUN_FIRST}, 
          state = EMISSION_RUN, chain_type = 4}
        class_closure = 0x7f6734881680
        handler_list = 0x7f6728665850
        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>


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

Comment 3 Chris Campbell 2009-12-17 16:57:01 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.