Bug 1254605

Summary: [abrt] telepathy-mission-control: g_malloc(): mission-control-5 killed by SIGTRAP
Product: [Fedora] Fedora Reporter: piio <bugzilla>
Component: telepathy-mission-controlAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: bdpepple, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/da30d6d7cb6feec9f6b8baa2528472f6dec48950
Whiteboard: abrt_hash:167101cc34a3dde3c1196b19783a2a3bf393710d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 12:09:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace
File: cgroup
File: core_backtrace
File: dso_list
File: environ
File: limits
File: maps
File: mountinfo
File: namespaces
File: open_fds
File: proc_pid_status
File: var_log_messages none

Description piio 2015-08-18 13:32:39 UTC
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/libexec/mission-control-5
crash_function: g_malloc
executable:     /usr/libexec/mission-control-5
global_pid:     3428
kernel:         4.2.0-0.rc7.git0.1.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 piio 2015-08-18 13:32:42 UTC
Created attachment 1064312 [details]
File: backtrace

Comment 2 piio 2015-08-18 13:32:43 UTC
Created attachment 1064313 [details]
File: cgroup

Comment 3 piio 2015-08-18 13:32:45 UTC
Created attachment 1064314 [details]
File: core_backtrace

Comment 4 piio 2015-08-18 13:32:46 UTC
Created attachment 1064315 [details]
File: dso_list

Comment 5 piio 2015-08-18 13:32:47 UTC
Created attachment 1064316 [details]
File: environ

Comment 6 piio 2015-08-18 13:32:48 UTC
Created attachment 1064317 [details]
File: limits

Comment 7 piio 2015-08-18 13:32:50 UTC
Created attachment 1064318 [details]
File: maps

Comment 8 piio 2015-08-18 13:32:51 UTC
Created attachment 1064319 [details]
File: mountinfo

Comment 9 piio 2015-08-18 13:32:52 UTC
Created attachment 1064320 [details]
File: namespaces

Comment 10 piio 2015-08-18 13:32:53 UTC
Created attachment 1064321 [details]
File: open_fds

Comment 11 piio 2015-08-18 13:32:55 UTC
Created attachment 1064322 [details]
File: proc_pid_status

Comment 12 piio 2015-08-18 13:32:56 UTC
Created attachment 1064323 [details]
File: var_log_messages

Comment 13 piio 2016-02-24 07:29:02 UTC
The problem still happens:

msg = 0x7fe6340008c0 "gmem.c:100: failed to allocate 18446744073709551581 bytes"
msg_alloc = 0x7fe6340008c0 "gmem.c:100: failed to allocate 18446744073709551581 bytes"

Comment 14 Jan Kurik 2016-02-24 13:38:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:

Comment 15 Fedora End Of Life 2017-07-25 19:10:39 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 16 Fedora End Of Life 2017-08-08 12:09:14 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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

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