Bug 886171 - [abrt] tracker-0.14.4-1.fc18: g_realloc: Process /usr/libexec/tracker-extract was killed by signal 11 (SIGSEGV)
Summary: [abrt] tracker-0.14.4-1.fc18: g_realloc: Process /usr/libexec/tracker-extract...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tracker
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a39d85982ec4bb132ee1547f776...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-11 16:54 UTC by Alex Markley
Modified: 2014-02-05 13:48 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 13:48:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (61.27 KB, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: cgroup (127 bytes, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: core_backtrace (2.25 KB, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: dso_list (12.44 KB, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: environ (1008 bytes, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: maps (66.46 KB, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: open_fds (5.62 KB, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: proc_pid_status (931 bytes, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details
File: var_log_messages (329 bytes, text/plain)
2012-12-11 16:54 UTC, Alex Markley
no flags Details

Description Alex Markley 2012-12-11 16:54:34 UTC
Description of problem:
First login after restoring home directory backup from working Fedora 17 system.

Version-Release number of selected component:
tracker-0.14.4-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/tracker-extract
crash_function: g_realloc
executable:     /usr/libexec/tracker-extract
kernel:         3.6.9-4.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #4 g_realloc at gmem.c:224
 #5 g_string_maybe_expand at gstring.c:107
 #6 g_string_insert_len at gstring.c:480
 #8 tracker_sparql_builder_object at /home/martyn/Source/tracker/src/libtracker-sparql/tracker-builder.vala:488
 #9 tracker_sparql_builder_object_int64 at /home/martyn/Source/tracker/src/libtracker-sparql/tracker-builder.vala:596
 #10 tracker_extract_get_metadata at tracker-extract-png.c:900
 #11 get_file_metadata at tracker-extract.c:375
 #12 get_metadata at tracker-extract.c:588
 #13 dispatch_task_cb at tracker-extract.c:721

Potential duplicate: bug 832585

Comment 1 Alex Markley 2012-12-11 16:54:36 UTC
Created attachment 661558 [details]
File: backtrace

Comment 2 Alex Markley 2012-12-11 16:54:38 UTC
Created attachment 661559 [details]
File: cgroup

Comment 3 Alex Markley 2012-12-11 16:54:40 UTC
Created attachment 661560 [details]
File: core_backtrace

Comment 4 Alex Markley 2012-12-11 16:54:41 UTC
Created attachment 661561 [details]
File: dso_list

Comment 5 Alex Markley 2012-12-11 16:54:43 UTC
Created attachment 661562 [details]
File: environ

Comment 6 Alex Markley 2012-12-11 16:54:45 UTC
Created attachment 661563 [details]
File: limits

Comment 7 Alex Markley 2012-12-11 16:54:47 UTC
Created attachment 661564 [details]
File: maps

Comment 8 Alex Markley 2012-12-11 16:54:49 UTC
Created attachment 661565 [details]
File: open_fds

Comment 9 Alex Markley 2012-12-11 16:54:51 UTC
Created attachment 661566 [details]
File: proc_pid_status

Comment 10 Alex Markley 2012-12-11 16:54:53 UTC
Created attachment 661567 [details]
File: var_log_messages

Comment 11 Edouard Lefebvre 2013-01-31 16:24:07 UTC
Same problem here.

Comment 12 E. Lewis 2013-02-13 19:53:21 UTC
This problem comes up randomly from time to time. A few days ago, it came up 5 times in in a a couple of hours. Today it has come up twice, both times in the last hour or so. It seems to have no impact on system performance. To me, it is more a nuisance issue than anything else, I have spent no time troubleshooting.

backtrace_rating: 4
Package: tracker-0.14.4-1.fc18
Architecture: i686
OS Release: Fedora release 18 (Spherical Cow)

Comment 13 Fedora End Of Life 2013-12-21 09:51:29 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 14 Fedora End Of Life 2014-02-05 13:48:19 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


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