Bug 1132685

Summary: [abrt] gvfs: g_realloc(): gvfsd-metadata killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jason Herring <jaherring>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alexl, bnocera, oholy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d09eef40c65d342d880d41b0983d139fc76cf43d
Whiteboard: abrt_hash:83cccda32c66495320a9a4f2f03da92c23050b44
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:11:16 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jason Herring 2014-08-21 19:46:40 UTC 
Description of problem:
No idea - I was scrolling in a browser window when my X session (Gnome/Cinnamon) crashed.  When I logged back in ABRT popped this up.

Version-Release number of selected component:
gvfs-1.18.3-2.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-metadata
crash_function: g_realloc
executable:     /usr/libexec/gvfsd-metadata
kernel:         3.15.10-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            6669

Truncated backtrace:
Thread no. 1 (8 frames)
 #4 g_realloc at gmem.c:169
 #5 g_string_maybe_expand at gstring.c:107
 #6 g_string_set_size at gstring.c:400
 #7 meta_builder_create_new_journal at metabuilder.c:1004
 #8 meta_builder_write at metabuilder.c:1146
 #9 meta_tree_flush_locked at metatree.c:2298
 #10 meta_tree_flush at metatree.c:2315
 #11 writeout_timeout at meta-daemon.c:62
Comment 1 Jason Herring 2014-08-21 19:46:42 UTC 
Created attachment 929335 [details]
File: backtrace
Comment 2 Jason Herring 2014-08-21 19:46:43 UTC 
Created attachment 929336 [details]
File: cgroup
Comment 3 Jason Herring 2014-08-21 19:46:43 UTC 
Created attachment 929337 [details]
File: core_backtrace
Comment 4 Jason Herring 2014-08-21 19:46:44 UTC 
Created attachment 929338 [details]
File: dso_list
Comment 5 Jason Herring 2014-08-21 19:46:44 UTC 
Created attachment 929339 [details]
File: environ
Comment 6 Jason Herring 2014-08-21 19:46:45 UTC 
Created attachment 929340 [details]
File: exploitable
Comment 7 Jason Herring 2014-08-21 19:46:45 UTC 
Created attachment 929341 [details]
File: limits
Comment 8 Jason Herring 2014-08-21 19:46:46 UTC 
Created attachment 929342 [details]
File: maps
Comment 9 Jason Herring 2014-08-21 19:46:47 UTC 
Created attachment 929343 [details]
File: open_fds
Comment 10 Jason Herring 2014-08-21 19:46:47 UTC 
Created attachment 929344 [details]
File: proc_pid_status
Comment 11 Jason Herring 2014-08-21 19:46:48 UTC 
Created attachment 929345 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 12:41:59 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 13 Fedora End Of Life 2015-06-29 22:11:16 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.