Version-Release number of selected component: gvfs-1.18.3-2.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-metadata crash_function: g_malloc executable: /usr/libexec/gvfsd-metadata kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #2 g_malloc at gmem.c:104 #3 g_strdup at gstrfuncs.c:364 #4 metadata_new at metabuilder.c:124 #5 metafile_key_set_value at metabuilder.c:378 #6 copy_tree_to_builder at metatree.c:2148 #8 meta_tree_flush_locked at metatree.c:2293 #9 meta_tree_flush at metatree.c:2315 #10 writeout_timeout at meta-daemon.c:62
Created attachment 857691 [details] File: backtrace
Created attachment 857692 [details] File: cgroup
Created attachment 857693 [details] File: core_backtrace
Created attachment 857694 [details] File: dso_list
Created attachment 857695 [details] File: environ
Created attachment 857696 [details] File: exploitable
Created attachment 857697 [details] File: limits
Created attachment 857698 [details] File: maps
Created attachment 857699 [details] File: open_fds
Created attachment 857700 [details] File: proc_pid_status
Created attachment 857701 [details] File: var_log_messages
Since there are no reports, I suspect this was due to system instability due to RAM timing issues on a new system which should now be fixed. Closing, will reopen if it recurs.