Launchpad has imported 17 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=10596.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2014-01-02T16:39:00+00:00 Lukaswhl wrote: Thunar crashes now and then with a segmentation fault. Steps to Reproduce: 1) Start thunar. 2) Wait. No specific action is required for thunar to crash. I just have to wait a few minutes and thunar crashes. Output in console says "Segmentation fault (core dumped)", there is no core file though. Executing generate-core-file in gdb outputs "Couldn't get registers: No such process." Output of "bt full" in gdb: #0 0x00007ffff4bca887 in g_slice_alloc () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #1 0x00007ffff4bcad5e in g_slice_alloc0 () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #2 0x00007ffff4bad244 in g_source_new () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #3 0x00007ffff4bb00a9 in g_timeout_source_new () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #4 0x00007ffff510a4c2 in ?? () from /usr/lib/libgio-2.0.so.0 No symbol table info available. #5 0x00007ffff4bafdf3 in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #6 0x00007ffff4baf296 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #7 0x00007ffff4baf5e8 in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #8 0x00007ffff4baf9ea in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #9 0x00007ffff6a3b9d7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #10 0x0000000000424262 in main (argc=1, argv=0x7fffffffe538) at main.c:310 session_client = 0xc84b40 dbus_service = 0x0 application = 0x7e76c0 error = 0x0 working_directory = 0x7f5820 "XSMP" filenames = 0x7f59e0 startup_id = 0x0 Any help getting more detailed debug info would be appreciated. Thunar version 1.6.3git-fc4a4b6 crashes as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/6 ------------------------------------------------------------------------ On 2014-02-24T05:51:56+00:00 Alistair Buxton wrote: We are seeing this type of crash reported several hundred times per day in Xubuntu with the automatic error reporting. However, you seem to be the only person who can reproduce it reliably. It is crashing inside the glib memory allocator which indicates random memory corruption in a totally different part of the code, and seems to give many different types of crash. Please install debugging symbols for glib and gtk to get the missing symbols filled in, then redo the stack trace. Then please run it in valgrind like this: G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --num-callers=40 --track-origins=yes --log-file=valgrind.log thunar And then attach valgrind.log. It will run really slow, don't worry about that. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/8 ------------------------------------------------------------------------ On 2014-02-24T05:53:35+00:00 Alistair Buxton wrote: Also is there anything unusual about the way you're running thunar? Are you leaving it open on a directory where the files are constantly changing? strace may also be useful, to see what activity it is doing leading up to the crash. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/9 ------------------------------------------------------------------------ On 2014-02-24T22:16:02+00:00 Alistair Buxton wrote: Another thing to try is: G_SLICE=debug-blocks gdb thunar Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/10 ------------------------------------------------------------------------ On 2014-02-28T19:49:28+00:00 Lukaswhl wrote: I was about to investigate this further today, but (un?)fortunately the random crashing has stopped. Suddenly everything's fine. Somehow I'm feeling unsatisfied now. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/11 ------------------------------------------------------------------------ On 2014-04-01T17:14:11+00:00 Lukaswhl wrote: Crashing has started again. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/13 ------------------------------------------------------------------------ On 2014-04-01T17:17:51+00:00 Lukaswhl wrote: The crashing has started again. However I'm unable to attach any logs, I get logged out by the site repeatedly. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/14 ------------------------------------------------------------------------ On 2014-04-01T17:19:44+00:00 Lukaswhl wrote: Created attachment 5406 GDB trace log Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/15 ------------------------------------------------------------------------ On 2014-04-01T17:24:36+00:00 Lukaswhl wrote: Created attachment 5407 Valgrind log Thunar did not crash when running with valgrind. I just quit thunar and attached the log anyway, as it may still be helpful. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/16 ------------------------------------------------------------------------ On 2014-04-01T17:27:23+00:00 Alistair Buxton wrote: These logs are no use out of context. How did you run it? How did it crash? What signal was received? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/17 ------------------------------------------------------------------------ On 2014-04-01T17:32:11+00:00 Lukaswhl wrote: Couldn't you just read my initial bug report? Everything necessary should be in there. GDB log created with "gdb thunar", in gdb console "r". I ran valgrind just the way you told me to. Crash is a segmentation fault. That's it, or did I miss something? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/18 ------------------------------------------------------------------------ On 2014-04-01T17:35:55+00:00 Alistair Buxton wrote: Are you saying that the crash is reproducable but NOT if you run it with the valgrind command? Or did it just crash once and now you can't reproduce it at all? Please try the command from comment 3. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/19 ------------------------------------------------------------------------ On 2014-04-01T17:51:49+00:00 Lukaswhl wrote: I can reproduce it, the crash occurs usually within 10 seconds to two minutes. I ran it with valgrind for ~10 minutes, then gave up. Somehow I missed your comment 3, sorry. I'll attach a new log. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/20 ------------------------------------------------------------------------ On 2014-04-01T17:53:25+00:00 Lukaswhl wrote: Created attachment 5408 G_SLICE=debug-blocks gdb thunar Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/21 ------------------------------------------------------------------------ On 2014-04-01T17:55:20+00:00 Lukaswhl wrote: Created attachment 5409 G_SLICE=debug-blocks gdb thunar Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/22 ------------------------------------------------------------------------ On 2014-04-01T18:07:05+00:00 Alistair Buxton wrote: That is really weird. Everything is consistent with memory corruption caused by mismatch between memory allocators - forcing it to always use malloc prevents the crash. But your last log crashes while allocating. G_SLICE=debug-blocks should cause a crash on deallocation. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/23 ------------------------------------------------------------------------ On 2014-04-02T16:05:29+00:00 Lukaswhl wrote: Please let me know if I can help any further. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1203296/comments/24 ** Changed in: thunar Status: Unknown => Confirmed ** Changed in: thunar Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203296 Title: thunar crashed with SIGSEGV in magazine_chain_pop_head() To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1203296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
