Summary: | Frequent seg faults when using NNTP | ||||||
---|---|---|---|---|---|---|---|
Product: | Claws Mail (GTK 2) | Reporter: | Marvin <marvint.roebuck> | ||||
Component: | NNTP | Assignee: | users | ||||
Status: | NEW --- | ||||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.11.0 | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Attachments: |
|
Description
Marvin
2014-11-09 01:05:40 UTC
Followed the intsructions but could not get a crash. I suspect that gdb serializes away the code path that leads to a crash. I could not get a crash just running without gdb either though. So -g might also effect the outcome. Perhaps that's a clue but not much of one I know. I'll try gdb -p <pid> and see if that is different. If you have any other ideas I will try them if I'm able. Created attachment 1449 [details]
thread-apply-all-bt
This is in 3.11.1 it is definitely an issue when the network is saturated by utilizing downstream bandwidth. This was not with -g unfortunately. These seem to be the significant entries from stdout gtkcmctree.c:3668 Condition node != NULL failed traceback: 0: /bin/claws-mail(gtk_cmctree_expand+0x158) 24: /bin/claws-mail(grouplist_dialog+0x965) Also from the kernel: traps: claws-mail[19393] general protection ip:7f2982695830 sp:7f297ea319c8 error:0 in libetpan.so.17.1.0 Do to freq. of crashes while using nntp I'm guessing the feature is not used by many others. |