Bug 1133924

Summary: tracker-extract is SIGABRTing due to setrlimits()
Product: [Fedora] Fedora Reporter: Vadim Rutkovsky <vrutkovs>
Component: trackerAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: baguzzzaji, charles.tryon, ch, dadreggors, dakingun, davidzgumberg, debarshir, ed.greshko, emmanuel.pacaud, esalvati, guillaumepoiriermorency, ifoolb, ignatenko, james, lkundrak, mgautier, minkov.89, mnowak, petersen, sanzoh, sumitkbhardwaj, tenpin784, vpodzime
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/bd20c3526f0a358fa0734ffcd9579201ee55a7ab
Whiteboard: abrt_hash:e1a4ef7b3da5b8a554d50a5c1b36cd4372440e4c
Fixed In Version: tracker-1.2.4-2.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-15 09:21:01 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 Vadim Rutkovsky 2014-08-26 13:00:11 UTC 
Version-Release number of selected component:
tracker-1.1.3-1.fc21

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-extract
crash_function: _g_log_abort
executable:     /usr/libexec/tracker-extract
kernel:         3.16.1-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _g_log_abort at gmessages.c:317
 #5 g_malloc0 at gmem.c:132
 #6 thread_memory_from_self at gslice.c:519
 #7 g_slice_alloc at gslice.c:985
 #8 g_string_sized_new at gstring.c:121
 #9 g_string_new at gstring.c:148
 #10 g_log_default_handler at gmessages.c:1403
 #11 tracker_log_handler at tracker-log.c:142
 #14 g_malloc0 at gmem.c:132
 #15 thread_memory_from_self at gslice.c:519
Comment 1 Vadim Rutkovsky 2014-08-26 13:00:16 UTC 
Created attachment 930942 [details]
File: backtrace
Comment 2 Vadim Rutkovsky 2014-08-26 13:00:17 UTC 
Created attachment 930943 [details]
File: cgroup
Comment 3 Vadim Rutkovsky 2014-08-26 13:00:19 UTC 
Created attachment 930944 [details]
File: core_backtrace
Comment 4 Vadim Rutkovsky 2014-08-26 13:00:20 UTC 
Created attachment 930945 [details]
File: dso_list
Comment 5 Vadim Rutkovsky 2014-08-26 13:00:22 UTC 
Created attachment 930946 [details]
File: environ
Comment 6 Vadim Rutkovsky 2014-08-26 13:00:23 UTC 
Created attachment 930947 [details]
File: limits
Comment 7 Vadim Rutkovsky 2014-08-26 13:00:25 UTC 
Created attachment 930948 [details]
File: maps
Comment 8 Vadim Rutkovsky 2014-08-26 13:00:26 UTC 
Created attachment 930949 [details]
File: open_fds
Comment 9 Vadim Rutkovsky 2014-08-26 13:00:29 UTC 
Created attachment 930950 [details]
File: proc_pid_status
Comment 10 Vadim Rutkovsky 2014-08-26 13:00:30 UTC 
Created attachment 930951 [details]
File: var_log_messages
Comment 11 Debarshi Ray 2014-11-10 14:55:53 UTC 
The tracker from thread 1 tells the story - malloc is complaining that it "failed to allocate %lu bytes" of memory.

Tracker-extract sets some resource limits on itself to limit the amount of memory that it can consume. The idea was to prevent a buggy or low quality extractor from going haywire and consuming a lot of resources on encountering a 'weird' file.

Unfortunately, papering over deficiencies in the extraction libraries like this does not work very well, and the only solution is to fix them. You can look at the upstream bug for further discussion: https://bugzilla.gnome.org/show_bug.cgi?id=737663

So, I will just go ahead and backport this from master to f21.

commit 4aea6025d02fcedffde688c6e9afe7736fea73bc
Author: Martyn Russell <martyn>
Date:   Mon Oct 13 11:41:57 2014 +0100

    tracker-extract: Avoid the use of setrlimit() it's causing problems
    
    Part of the solution is this commit, see:
    https://bugzilla.gnome.org/show_bug.cgi?id=737663
    
    The other part is to use cgroups
Comment 12 Fedora Update System 2014-11-10 15:50:45 UTC 
tracker-1.2.4-2.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/tracker-1.2.4-2.fc21
Comment 13 Fedora Update System 2014-11-12 02:38:09 UTC 
Package tracker-1.2.4-2.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tracker-1.2.4-2.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-14739/tracker-1.2.4-2.fc21
then log in and leave karma (feedback).
Comment 14 Fedora Update System 2014-11-15 09:21:01 UTC 
tracker-1.2.4-2.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.