Bug 1044615

Summary: [abrt] ekiga: (anonymous namespace)::__freelist::~__freelist(): ekiga killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Christian Kujau <redhat>
Component: ekigaAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: akurtako, alexander.wajda, eugen.dedu, paul.destefano-redhat2, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9fc7d36592e3392d46d1a06502b5a5d292d6e9cf
Whiteboard: abrt_hash:5f9cc3121e20880ffe9dd1265af6668d8ada04d9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 13:35:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Christian Kujau 2013-12-18 16:59:54 UTC
Description of problem:
unknown

Version-Release number of selected component:
ekiga-4.0.1-6.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 3
cmdline:        ekiga
crash_function: (anonymous namespace)::__freelist::~__freelist
executable:     /usr/bin/ekiga
kernel:         3.11.10-301.fc20.x86_64
runlevel:       3 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #2 (anonymous namespace)::__freelist::~__freelist at ../../../../../libstdc++-v3/src/c++98/mt_allocator.cc:50
 #3 __cxa_finalize at cxa_finalize.c:56
 #4 __do_global_dtors_aux at /lib64/libstdc++.so.6
 #5 ??
 #6 _dl_fini at dl-fini.c:252

Comment 1 Christian Kujau 2013-12-18 16:59:57 UTC
Created attachment 838437 [details]
File: backtrace

Comment 2 Christian Kujau 2013-12-18 16:59:59 UTC
Created attachment 838438 [details]
File: cgroup

Comment 3 Christian Kujau 2013-12-18 17:00:00 UTC
Created attachment 838439 [details]
File: core_backtrace

Comment 4 Christian Kujau 2013-12-18 17:00:02 UTC
Created attachment 838440 [details]
File: dso_list

Comment 5 Christian Kujau 2013-12-18 17:00:03 UTC
Created attachment 838441 [details]
File: environ

Comment 6 Christian Kujau 2013-12-18 17:00:05 UTC
Created attachment 838442 [details]
File: exploitable

Comment 7 Christian Kujau 2013-12-18 17:00:07 UTC
Created attachment 838443 [details]
File: limits

Comment 8 Christian Kujau 2013-12-18 17:00:08 UTC
Created attachment 838444 [details]
File: maps

Comment 9 Christian Kujau 2013-12-18 17:00:09 UTC
Created attachment 838445 [details]
File: open_fds

Comment 10 Christian Kujau 2013-12-18 17:00:11 UTC
Created attachment 838446 [details]
File: proc_pid_status

Comment 11 Christian Kujau 2013-12-18 17:00:15 UTC
Created attachment 838447 [details]
File: var_log_messages

Comment 12 Eugen Dedu 2013-12-23 09:51:04 UTC
Christian, were you quitting ekiga when this crash appeared?

Is it reproducible 100% or not?

Comment 13 Christian Kujau 2013-12-25 03:46:18 UTC
No, it's not reproducible so far. And I don't know if I was quiting ekiga when the crash appeared, but I don't think I was.

Comment 14 Alex Wajda 2014-02-09 11:26:38 UTC
Another user experienced a similar problem:

How to reproduce -- just use it often enough and it will crash sometimes with no obvious reason.

reporter:       libreport-2.1.12
backtrace_rating: 3
cmdline:        ekiga
crash_function: (anonymous namespace)::__freelist::~__freelist
executable:     /usr/bin/ekiga
kernel:         3.12.9-301.fc20.x86_64
package:        ekiga-4.0.1-6.fc20
reason:         ekiga killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 15 Eugen Dedu 2014-02-12 16:50:34 UTC
Hum, difficult to investigate, somehow a memory corruption somewhere in the program...

I suggest waiting until the next major ekiga release (or its preliminary releases) will appear, hopefully it has been fixed during this rich development cycle.

Comment 16 Fedora End Of Life 2015-05-29 10:01:58 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 17 Fedora End Of Life 2015-06-29 13:35:35 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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