Description of problem: Deleted 3 mails on IMAP server, pressed x for Expunge, program crashed. Version-Release number of selected component: claws-mail-3.9.3-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: claws-mail crash_function: pango_parse_markup executable: /usr/bin/claws-mail kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 pango_parse_markup at /lib64/libpango-1.0.so.0 #6 gtk_label_recalculate at /lib64/libgtk-x11-2.0.so.0 #7 gtk_label_set_markup at /lib64/libgtk-x11-2.0.so.0 #8 gtk_tooltip_set_markup at /lib64/libgtk-x11-2.0.so.0 #9 gtk_tooltip_run_requery at /lib64/libgtk-x11-2.0.so.0 #10 _gtk_tooltip_handle_event at /lib64/libgtk-x11-2.0.so.0 #11 gtk_main_do_event at /lib64/libgtk-x11-2.0.so.0 #12 gdk_event_dispatch at /lib64/libgdk-x11-2.0.so.0 #14 g_main_context_iterate.isra.24 at /lib64/libglib-2.0.so.0 #16 gtk_main at /lib64/libgtk-x11-2.0.so.0
Created attachment 857193 [details] File: backtrace
Created attachment 857194 [details] File: cgroup
Created attachment 857195 [details] File: core_backtrace
Created attachment 857196 [details] File: dso_list
Created attachment 857197 [details] File: environ
Created attachment 857198 [details] File: limits
Created attachment 857199 [details] File: maps
Created attachment 857200 [details] File: open_fds
Created attachment 857201 [details] File: proc_pid_status
Created attachment 857202 [details] File: var_log_messages
> Deleted 3 mails on IMAP server, pressed x for Expunge, program crashed. But not reproducibly, as it may only be a side-effect of something else having gone wrong earlier. Parts of IMAP access in Claws Mail can become unstable when facing networking interruptions, for example. > #0 0x0000003c5c835c59 in raise () from /lib64/libc.so.6 > No symbol table info available. > #1 0x0000003c5c837368 in abort () from /lib64/libc.so.6 > No symbol table info available. > #2 0x0000003c5c875da4 in __libc_message () from /lib64/libc.so.6 > No symbol table info available. > #3 0x0000003c5c87d098 in _int_free () from /lib64/libc.so.6 > No symbol table info available. > #4 0x0000003c5f44ef7f in g_free () from /lib64/libglib-2.0.so.0 > No symbol table info available. The submitted backtrace is corrupted/incomplete (= lacking details). One can see that it ran into a fatal memory management problem upon trying to free allocated memory (and glibc took down the application as a result).
That's ABRT's brilliant UI. After realizing how big the core was (I'd upload it by tomorrow, hehe), I wanted to go back to the option with downloading debuginfo but couldn't find a way. Next time I'll make sure to provide full backtrace. Sorry about this.