Bug 3390

Summary: display intermittantly unresponsive (freezes) after trying to open or delete message
Product: Claws Mail (GTK 2) Reporter: Ron Schwiesow <nanron62>
Component: UIAssignee: users
Status: RESOLVED INVALID    
Severity: normal    
Priority: P3    
Version: 3.11.1   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
backtrace after display freezes none

Description Ron Schwiesow 2015-02-23 21:13:56 UTC
Created attachment 1487 [details]
backtrace after display freezes

OS is Debian Jessie.

Display (UI) freezes when trying to open or delete a message. Happens intermittantly, but some messages seem bad and the freeze often repeats on them. When miniminizing display and then re-displaying, the screen is gray. No response to close application. Can kill application, but it can't be reopened. On reboot command, the shutdown message appears to have a problem, but it goes so fast that I can't follow it.

Followed instructions in Debugging Claws using gdb. Does not crash with a segmentation fault (see backtrace) but needs to be stopped with ^C. Backtrace attached.
Comment 1 Paul 2015-02-24 09:04:31 UTC
How long do you wait before killing it? Show the --debug output without killing it. At this point I suspect a corrupted image attachment.
Comment 2 Ron Schwiesow 2015-02-28 00:53:37 UTC
I kill it quite soon after it freezes. With the help of your comment, I waited about 10 min and it sorted itself out. I'll try a debug without killing it. Is ^C on the terminal the same as "kill" on right click?

And yes, usually the bad email often (perhaps always) has some sort of image. But my wife's MSWindows 7 with another e-mail application seems to open the offending e-mails OK.
Comment 3 Paul 2015-02-28 08:08:49 UTC
(In reply to comment #2)
> And yes, usually the bad email often (perhaps always) has some sort of
> image. But my wife's MSWindows 7 with another e-mail application seems to
> open the offending e-mails OK.

Your wife's email application is , no doubt, not reliant on libgdk-pixbuf, which it looks is where the bug resides.
Comment 4 Ron Schwiesow 2015-02-28 19:10:06 UTC
Thank you for the analysis. That points me where to look. Thanks!