Version-Release number of selected component: tracker-0.16.0-1.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/tracker-extract crash_function: g_malloc executable: /usr/libexec/tracker-extract kernel: 3.9.0-0.rc8.git0.2.fc19.i686.PAE runlevel: N 5 uid: 1000 ureports_counter: 2 Truncated backtrace: Thread no. 1 (10 frames) #2 g_malloc at gmem.c:164 #3 g_slice_alloc at gslice.c:1003 #4 _default_mem_new_block at gstallocator.c:410 #5 gst_allocator_alloc at gstallocator.c:307 #6 gst_buffer_new_allocate at gstbuffer.c:621 #7 gst_base_src_default_alloc at gstbasesrc.c:1385 #8 gst_base_src_default_create at gstbasesrc.c:1423 #9 gst_base_src_get_range at gstbasesrc.c:2355 #10 gst_base_src_getrange at gstbasesrc.c:2522 #11 gst_pad_get_range_unchecked at gstpad.c:4058
Created attachment 741227 [details] File: backtrace
Created attachment 741230 [details] File: cgroup
Created attachment 741232 [details] File: core_backtrace
Created attachment 741233 [details] File: dso_list
Created attachment 741235 [details] File: environ
Created attachment 741237 [details] File: limits
Created attachment 741240 [details] File: maps
Created attachment 741242 [details] File: open_fds
Created attachment 741244 [details] File: proc_pid_status
Created attachment 741247 [details] File: var_log_messages
The error happened just as I was booting up for the first time, with a clean install. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/tracker-extract crash_function: g_malloc executable: /usr/libexec/tracker-extract kernel: 3.9.5-301.fc19.x86_64 package: tracker-0.16.1-3.fc19 reason: Process /usr/libexec/tracker-extract was killed by signal 5 (SIGTRAP) runlevel: N 5 uid: 1000
With my new installation of F19 this bug affected me quite severely. Tracker just kept crashing and I got 54 crash notifications when I had left my computer for half an hour. Tracker starting eating memory like it was anticipating a famine, and I had to restart my box. After the restart it seemed to continue crashing right after logging in to GNOME Shell again, so I had to kill all tracker processes manually to be able to work on my box. Considering that this bug was already reported in in April, I'd very much appreciate it if any developer could take a look at this.
This tracker issue was annoying me so much that I was about to switch to another distribution. Fortunately however, since tracker 1.6.2 was downloaded through the Fedora 19 updates today I haven't been able to reproduce this bug. Can anyone else confirm, so that this bug might be closed?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hi, thank you for this bug. Now we have in repos 1.0.2 so I think you can't reproduce this bug. If you can - please re-open!