GNOME Bugzilla – Bug 704048
[abrt] tracker-0.16.0-1.fc19: g_wakeup_new: Process /usr/libexec/tracker-extract was killed by signal 5 (SIGTRAP)
Last modified: 2013-07-30 10:52:07 UTC
From https://bugzilla.redhat.com/show_bug.cgi?id=959020: 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_wakeup_new executable: /usr/libexec/tracker-extract kernel: 3.9.0-301.fc19.x86_64 runlevel: N 5 uid: 1000 ureports_counter: 1 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #2 g_wakeup_new at gwakeup.c:163 #3 g_cancellable_make_pollfd at gcancellable.c:406 #4 socket_source_new at gsocket.c:3265 #5 g_socket_create_source at gsocket.c:3330 #6 _g_socket_read_with_control_messages at gdbusprivate.c:201 #7 _g_dbus_worker_do_read_unlocked at gdbusprivate.c:861 #8 _g_dbus_worker_do_read_cb at gdbusprivate.c:810 #9 g_simple_async_result_complete at gsimpleasyncresult.c:777 #10 complete_in_idle_cb at gsimpleasyncresult.c:789 #15 gdbus_shared_thread_func at gdbusprivate.c:278 See also: https://retrace.fedoraproject.org/faf/reports/84633/
Hello Michal, are you able to try with tracker 0.16.1 and tell me if you can reproduce this? Thanks.
Hi Martyn, that report in comment #0 is not mine but from the original Fedora reporter. However I was affected by that bug also, thought with 0.16.1 from Fedora 19. So, yes, I am able to reproduce it with latest stable tracker. I'll try to find the problem-triggering file if you want me to. Anyway, thanks for looking into this.
Created attachment 249062 [details] tracker-0.16.1 backtrace This is my original backtrace, can't reproduce it at the moment.
Now got the crash again but on another file. However tracker-extract won't crash on that file if run separately...
Clearly some sort of fd leak; look at the open_fds list attached to the downstream bug
Thanks for the tip Matthias. The extractor still has some 100 file descriptors in use on average (here), but that's better than the massive leak I found in the GStreamer extractor upon failure conditions. This will be fixed in 0.16.2 and 0.17.0. commit f696dcd00af962e4864ca38365af4f245752a5d5 Author: Martyn Russell <martyn@lanedo.com> Date: Fri Jul 19 20:36:43 2013 +0100 tracker-extract-gstreamer: Don't leak file descriptors & use up all FDs The GStreamer extractor was not calling all the shutdown functions internally to clean up streams in failure conditions. https://bugzilla.gnome.org/show_bug.cgi?id=704048 https://bugzilla.redhat.com/show_bug.cgi?id=741479
*** Bug 702592 has been marked as a duplicate of this bug. ***
Looks like it's only committed to master and, then, wouldn't be included in 1.16.2 :/ Thanks!
(In reply to comment #8) > Looks like it's only committed to master and, then, wouldn't be included in > 1.16.2 :/ > > Thanks! I merge all commits necessary from master to tracker-0.16 branch when doing the release - this will certainly be in there.