Not sure if it's related to Bug 7384 or not, but I felt it was different enough that it was worth filing as a separate bug. Tumblerd likes to hang on my system using up 100% of my CPU. The problem doesn't seem to require I had a thunar window open, and it doesn't seem to have any pattern that I could see. Thunar works fine during these crashes, however thumbnails don't generate obviously, however a few times I've had thunar freeze on me showing nothing but a blank directory inside an unresponsive window until I killed either it or/and tumblerd. Running on a Gentoo x86-64 system. Haven't done a proper debug using gdb, but I plan to it now. The segfault below is from dmesg. I have noticed that it will not always spit out segfault errors when it freezes on me, as I found out while tailing dmesg. It might also be worth noting that everything seemed to have worked fine until I switched from my Intel GPU to and nVidia 6600GT using the non-free drivers. tumblerd[32513]: segfault at 7f75817e09e3 ip 00007f75817e09e3 sp 00007f757cfe9e30 error 14 in libstdc++.so.6.0.14[7f7582ebe000+eb000] tumblerd[32514]: segfault at 7f75817e09e3 ip 00007f75817e09e3 sp 00007f757c7e8e30 error 14 in libstdc++.so.6.0.14[7f7582ebe000+eb000]
Have you tried to delete your ~/.thumbnails/ folder? It helped for some users due to broken png files.
(In reply to comment #1) > Have you tried to delete your ~/.thumbnails/ folder? It helped for some users > due to broken png files. That is not an acceptable solution, is it? Tumbler should not hang or crash in any case.
Please killall tumblerd instances, run "gdb <path to tumblerd>" and then run thunar to reproduce the crash. A backtrace would be really helpful.
(In reply to comment #2) > That is not an acceptable solution, is it? Tumbler should not hang or crash in > any case. I do fully agree. I just wanted to help from user to user. :o) Of course, it's better to fix the bug in upstream development to avoid such an issue in the near future and for other potential new users. Thanks for the great work here.
I lack essential information to be able to fix this bug. Please provide more details (such as which types of files make tumbler crash) and a backtrace of the crash.
I'm using tumblerd-0.1.27 here on a Vaio VPCF13 Laptop, gentoo-amd64, kernel-3.7.2, gcc-4.6.3. dmesg reports: [17282.122795] tumblerd[10901]: segfault at 0 ip 000000000040b8f8 sp 00007fff45731450 error 4 in tumblerd[400000+17000] [17283.348625] tumblerd[10908]: segfault at 0 ip 000000000040b8f8 sp 00007fff7866f2b0 error 4 in tumblerd[400000+17000] [17284.315029] tumblerd[10913]: segfault at 0 ip 000000000040b8f8 sp 00007fff0bc3f580 error 4 in tumblerd[400000+17000] [17289.225560] tumblerd[10949]: segfault at 0 ip 000000000040b8f8 sp 00007fff2b940da0 error 4 in tumblerd[400000+17000] [17292.057964] tumblerd[10971]: segfault at 0 ip 000000000040b8f8 sp 00007fff3a73ab00 error 4 in tumblerd[400000+17000] Then running tumblerd with gdb: Program received signal SIGSEGV, Segmentation fault. 0x000000000040b8f8 in tumbler_registry_get_thumbnailer_array () (gdb) bt #0 0x000000000040b8f8 in tumbler_registry_get_thumbnailer_array () #1 0x000000000040da64 in tumbler_service_queue () #2 0x000000000040cc63 in dbus_glib_marshal_tumbler_service_VOID__BOXED_BOXED_STRING_STRING_UINT_POINTER () #3 0x00007ffff7bc1f38 in object_registration_message () from /usr/lib64/libdbus-glib-1.so.2 #4 0x00007ffff7990efe in _dbus_object_tree_dispatch_and_unlock () from /usr/lib64/libdbus-1.so.3 #5 0x00007ffff7986876 in dbus_connection_dispatch () from /usr/lib64/libdbus-1.so.3 #6 0x00007ffff7bbf185 in message_queue_dispatch () from /usr/lib64/libdbus-glib-1.so.2 #7 0x00007ffff6ee7813 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #8 0x00007ffff6ee7b60 in g_main_context_iterate.isra.25 () from /usr/lib64/libglib-2.0.so.0 #9 0x00007ffff6ee7f5a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #10 0x0000000000406bda in main ()
Everything is fine on tumbler-0.1.25, no crashes !
Im affection the tumblerd crashes im using Xubuntu 13.04 amd64, tumbler 0.1.27 https://bugs.launchpad.net/ubuntu/+source/tumbler/+bug/1182058
Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... /usr/sbin/thumblerd: No such file or directory. (gdb) quit nmorozov@nmorozov:~$ tumblerd tumblerd: command not found nmorozov@nmorozov:~$ gdb /usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd...(no debugging symbols found)...done. (gdb) run Starting program: /usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff03c2700 (LWP 8365)] [New Thread 0x7fffef4d4700 (LWP 8366)] [New Thread 0x7fffeecd3700 (LWP 8367)] (tumblerd:8361): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed (tumblerd:8361): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed (tumblerd:8361): GStreamer-CRITICAL **: gst_element_get_bus: assertion `GST_IS_ELEMENT (element)' failed (tumblerd:8361): GStreamer-CRITICAL **: gst_bus_timed_pop_filtered: assertion `GST_IS_BUS (bus)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffef4d4700 (LWP 8366)] 0x00007ffff15c8b67 in ?? () from /usr/lib/x86_64-linux-gnu/tumbler-1/plugins/tumbler-gst-thumbnailer.so
(gdb) backtrace #0 0x00007ffff15c8b67 in ?? () from /usr/lib/x86_64-linux-gnu/tumbler-1/plugins/tumbler-gst-thumbnailer.so #1 0x000055555556459c in ?? () #2 0x00007ffff6f2a6f2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff6f29eb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007ffff6ca7f8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #5 0x00007ffff69d1e1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb)
killing ~/.thumbnails/ doen't help :((
-- GitLab Migration Automatic Message -- This bug has been migrated to xfce.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.xfce.org/xfce/tumbler/-/issues/4. Please create an account or use an existing account on one of our supported OAuth providers. If you want to fork to submit patches and merge requests please continue reading here: https://docs.xfce.org/contribute/dev/git/start#gitlab_forks_and_merge_requests Also feel free to reach out to us on the mailing list https://mail.xfce.org/mailman/listinfo/xfce4-dev