Bug #257

Crash opening particular message

Added by John Coppens over 2 years ago. Updated over 2 years ago.

Status:NewStart date:05/18/2016
Priority:NormalDue date:
Assignee:Hiroyuki Yamamoto% Done:

0%

Category:SylpheedSpent time:-
Target version:-

Description

Years ago, I had a similar problem, never found a solution.

Today the same issue happened again: Trying to open (=view) a message from the message folders,
Sylpheed hangs completely - no output at all. I ran Sylpheed from a terminal - no error messages,
or any text.

I ran the program from inside gdb, and have attached the backtrace. I also attached the
problematic message.

This is not a very big problem, except that when I have been reading other messages, the
'read' status of those is forgotten. It takes some searching to find the internal message
Sylpheed message number to delete that message and avoid future hangs.

sylpheed.bt - Backtrace (7.34 KB) John Coppens, 05/18/2016 02:32 AM

2355 - Problem message (7.07 KB) John Coppens, 05/18/2016 02:33 AM

History

#1 Updated by Hiroyuki Yamamoto over 2 years ago

John Coppens wrote:

Years ago, I had a similar problem, never found a solution.

Today the same issue happened again: Trying to open (=view) a message from the message folders,
Sylpheed hangs completely - no output at all. I ran Sylpheed from a terminal - no error messages,
or any text.

I ran the program from inside gdb, and have attached the backtrace. I also attached the
problematic message.

This is not a very big problem, except that when I have been reading other messages, the
'read' status of those is forgotten. It takes some searching to find the internal message
Sylpheed message number to delete that message and avoid future hangs.

I've checked the backtrace and the message.
It seems that the message contains S/MIME signature,
and Sylpheed seems to be stuck on verifying it.

#0  0x00007fffed9ddb53 in __select_nocancel () from /lib64/libc.so.6
#1  0x00007ffff7bcd9a9 in ?? () from /usr/lib64/libgpgme.so.11
#2  0x00007ffff7bca16c in ?? () from /usr/lib64/libgpgme.so.11
#3  0x00007ffff7bb319f in ?? () from /usr/lib64/libgpgme.so.11
#4  0x00007ffff7bb6a50 in gpgme_op_verify () from /usr/lib64/libgpgme.so.11
#5  0x00000000004d36f8 in check_signature (mimeinfo=<optimized out>, 
    fp=0xc32a00, partinfo=0x10dd600) at rfc2015.c:289

Could you provide information about your environment?
I couldn't reproduce it on Windows 7 and Ubuntu 14.04.

Also available in: Atom PDF