Bug 574001 - [abrt] crash in epiphany-2.28.2-1.fc12: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in epiphany-2.28.2-1.fc12: Process /usr/bin/epiphany was killed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: epiphany
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7f27b1aea42c6cef70bce2ca225...
: 532351 542685 591353 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-16 12:01 UTC by filip.slunecko
Modified: 2010-12-03 17:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 17:15:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.33 KB, text/plain)
2010-03-16 12:01 UTC, filip.slunecko
no flags Details

Description filip.slunecko 2010-03-16 12:01:27 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: epiphany
component: epiphany
executable: /usr/bin/epiphany
kernel: 2.6.32.9-70.fc12.x86_64
package: epiphany-2.28.2-1.fc12
rating: 4
reason: Process /usr/bin/epiphany was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. insert URL which leads to the file in MS share point portal
2.
3.

Comment 1 filip.slunecko 2010-03-16 12:01:30 UTC
Created attachment 400444 [details]
File: backtrace

Comment 2 Chris Campbell 2010-04-10 17:26:41 UTC
Thread 1 (Thread 6092):
#0  0x0000000000000000 in ?? ()
No symbol table info available.
#1  0x000000397328f30b in WebCore::finishedCallback (
    session=<value optimized out>, msg=0x17d9030 [SoupMessage], 
    data=<value optimized out>)
    at WebCore/platform/network/soup/ResourceHandleSoup.cpp:322
        handle = {<WTF::FastAllocBase> = {<No data fields>}, m_ptr = 
    0x7f524e57c380}
        d = 0x7f524aadbc00
        client = 0x7f524e5a9b00
#2  0x0000003ebb636e8d in final_finished (req=0x17d9030 [SoupMessage], 
    user_data=0x7f5244002de0) at soup-session-async.c:383
        item = 0x7f5244002de0
        session = 0x1147480 [SoupSessionAsync]
#3  0x0000003f6da0ba8e in IA__g_closure_invoke (closure=0x183b570, 
    return_value=0x0, n_param_values=1, param_values=0x183c920, 
    invocation_hint=0x7fffe9883f90) at gclosure.c:767
        marshal = <value optimized out>
        marshal_data = <value optimized out>
        in_marshal = <value optimized out>
        __PRETTY_FUNCTION__ = "IA__g_closure_invoke"
#4  0x0000003f6da214b0 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:3317
        tmp = <value optimized out>
        handler = 0x1812150
        emission = {next = 0x7fffe9884390, instance = 0x17d9030, ihint = {
            signal_id = 407, detail = 0, run_type = G_SIGNAL_RUN_LAST}, 
          state = EMISSION_RUN, chain_type = 4}
        handler_list = 0x180a380
        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>
#5  0x0000003f6da22259 in IA__g_signal_emit_valist (
    instance=<value optimized out>, signal_id=<value optimized out>, 
    detail=<value optimized out>, var_args=0x7fffe9884180) at gsignal.c:2980
        instance_and_params = <value optimized out>
        node = 0x179bbe0
        i = <value optimized out>
        __PRETTY_FUNCTION__ = "IA__g_signal_emit_valist"
#6  0x0000003f6da227a3 in IA__g_signal_emit (instance=<value optimized out>, 
    signal_id=<value optimized out>, detail=<value optimized out>)
    at gsignal.c:3037
        var_args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
    0x7fffe9884260, reg_save_area = 0x7fffe98841a0}}
#7  0x0000003ebb62d52f in soup_message_io_finished (msg=
    0x17d9030 [SoupMessage]) at soup-message-io.c:177
No locals.



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

Comment 3 Chris Campbell 2010-04-10 17:31:25 UTC
*** Bug 532351 has been marked as a duplicate of this bug. ***

Comment 4 Chris Campbell 2010-04-10 17:32:54 UTC
*** Bug 542685 has been marked as a duplicate of this bug. ***

Comment 5 Chris Campbell 2010-05-24 13:06:26 UTC
Reporter, is this crash reproducible?



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

Comment 6 filip.slunecko 2010-05-24 16:05:24 UTC
Yes. It crashes always, when I'm trying to load our company's sharepoint portal page.

Comment 7 Chris Campbell 2010-05-24 20:30:12 UTC

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

Comment 8 Karel Klíč 2010-05-25 10:23:53 UTC
*** Bug 591353 has been marked as a duplicate of this bug. ***

Comment 9 Bug Zapper 2010-11-03 19:32:34 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Bug Zapper 2010-12-03 17:15:13 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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