Hide Forgot
Description of problem: As far as I understand it has crashed when network connection was switched off. Version-Release number of selected component: claws-mail-3.9.2-7.fc19 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/claws-mail crash_function: re_search_internal executable: /usr/bin/claws-mail kernel: 3.10.10-200.fc19.i686.PAE runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 re_search_internal at regexec.c:711 #3 __regexec at regexec.c:250 #4 subject_get_prefix_length at utils.c:3824 #5 subject_table_lookup at utils.c:3716 #6 folder_item_scan_full at folder.c:2425 #7 folder_item_scan at folder.c:2501 #8 folderview_check_new at folderview.c:1197 #9 inc_all_account_mail at inc.c:379 #10 inc_autocheck_func at inc.c:1559 #16 gtk_main at gtkmain.c:1257
Created attachment 794796 [details] File: backtrace
Created attachment 794797 [details] File: cgroup
Created attachment 794798 [details] File: core_backtrace
Created attachment 794799 [details] File: dso_list
Created attachment 794800 [details] File: environ
Created attachment 794801 [details] File: exploitable
Created attachment 794802 [details] File: limits
Created attachment 794803 [details] File: maps
Created attachment 794804 [details] File: open_fds
Created attachment 794805 [details] File: proc_pid_status
Created attachment 794806 [details] File: var_log_messages
> As far as I understand it has crashed when network connection was switched off. Then it's the old instability when losing/interrupting networking, and the crash (in memory management) is just a side-effect. There are various upstream tickets about such crashes already. | #0 0x49544100 in _int_malloc (av=av@entry=0x49688420 <main_arena>, | bytes=bytes@entry=1048) at malloc.c:3631