Bug 1100297

Summary: [abrt] tracker: g_malloc(): tracker-extract killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Morgan Leijström <fri>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dakingun, debarshir, xiangjihan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2b4b5a032e5fdee037dce5b76f6c900bacd1786c
Whiteboard: abrt_hash:6015cf607f68328c5dd5e7424a68c4c886a35a04
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:46:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Morgan Leijström 2014-05-22 13:03:52 UTC
Description of problem:
1) Was using KDE
2) Installed cinnamon and mate
3) logged out of KDE
4) logged into cinnamon for the first time ever (on this reinstalled system)
- however it use a reused /home from a recent install of fc20 a couple weeks ago where i installed cinnemon, but i do not remember if i there logged into it or not.
Same computer as in https://bugzilla.redhat.com/show_bug.cgi?id=1096989 and Bug 1093959 
(sidenote: it would be good if this report tool could us emore CPU, now it took fifteen minutes or so idling away at 3 to 5% cpu!  (i did not dare shutting it down or suspending as the system have problems resuming)

Version-Release number of selected component:
tracker-0.16.4-2.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-extract
crash_function: g_malloc
executable:     /usr/libexec/tracker-extract
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            10703

Truncated backtrace:
Thread no. 1 (6 frames)
 #2 g_malloc at gmem.c:109
 #3 read_metadata at tracker-extract-gif.c:136
 #4 tracker_extract_get_metadata at tracker-extract-gif.c:666
 #5 get_file_metadata at tracker-extract.c:347
 #6 get_metadata at tracker-extract.c:552
 #7 dispatch_task_cb at tracker-extract.c:679

Potential duplicate: bug 759325

Comment 1 Morgan Leijström 2014-05-22 13:03:57 UTC
Created attachment 898379 [details]
File: backtrace

Comment 2 Morgan Leijström 2014-05-22 13:03:59 UTC
Created attachment 898380 [details]
File: cgroup

Comment 3 Morgan Leijström 2014-05-22 13:04:02 UTC
Created attachment 898381 [details]
File: core_backtrace

Comment 4 Morgan Leijström 2014-05-22 13:04:04 UTC
Created attachment 898382 [details]
File: dso_list

Comment 5 Morgan Leijström 2014-05-22 13:04:06 UTC
Created attachment 898383 [details]
File: environ

Comment 6 Morgan Leijström 2014-05-22 13:04:08 UTC
Created attachment 898384 [details]
File: limits

Comment 7 Morgan Leijström 2014-05-22 13:04:13 UTC
Created attachment 898385 [details]
File: maps

Comment 8 Morgan Leijström 2014-05-22 13:04:17 UTC
Created attachment 898386 [details]
File: open_fds

Comment 9 Morgan Leijström 2014-05-22 13:04:19 UTC
Created attachment 898387 [details]
File: proc_pid_status

Comment 10 Morgan Leijström 2014-05-22 13:04:21 UTC
Created attachment 898388 [details]
File: var_log_messages

Comment 11 项纪汉 2014-06-23 16:31:36 UTC
Another user experienced a similar problem:

It occured when I install php form source package.I was run the "./configure --......." process.I do not know the details.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-extract
crash_function: g_malloc
executable:     /usr/libexec/tracker-extract
kernel:         3.14.8-200.fc20.x86_64
package:        tracker-0.16.4-2.fc20
reason:         tracker-extract killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 12 Fedora Admin XMLRPC Client 2014-07-26 17:13:33 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Fedora Admin XMLRPC Client 2014-07-27 06:35:37 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 14 Fedora End Of Life 2015-05-29 11:55:51 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 15 Fedora End Of Life 2015-06-29 20:46:28 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.