Bug 2852 - UI hang at BIG send end
Summary: UI hang at BIG send end
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI (show other bugs)
Version: 3.9.1
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2013-01-11 17:02 UTC by Pierre Fortin
Modified: 2013-01-11 19:15 UTC (History)
0 users

See Also:


Attachments
screen shot of "hung" display (66.24 KB, image/jpeg)
2013-01-11 17:02 UTC, Pierre Fortin
no flags Details

Description Pierre Fortin 2013-01-11 17:02:06 UTC
Created attachment 1217 [details]
screen shot of "hung" display

POP3/SMTP only accounts.

Partially out of curiosity, I sent a LARGE email with 24 photos attached (almost 46MB before encoding).  It appears to have completed the send; but the interface is now mostly non-responsive.  Clicks and scrolling are ignored.

However, as the mouse moves over the header pane, tooltips showing the Subject pop up. I can window-shade, lower/raise the window and everything appears normal except for the otherwise "hung" state.

Not sure if CM is checking mail in bg; but I'm seeing these messages on the console (messages have been appearing for quite some time, so they appear "normal"). ===============================
** (claws-mail:23304): WARNING **: xml_parse_next_tag(): Can't parse next tag


** (claws-mail:23304): WARNING **: no node
=================================

In the screen shot, the progress bar is gone, Queue is still showing message, and status bar still has 'Sending...'

I can leave it for another hour or so in case someone wants me to try something...
Comment 1 Pierre Fortin 2013-01-11 19:15:15 UTC
ARRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGGHHHHHHHHHHHHHHHHHHH!!!!   :) :)

Doing too many things at once...  turns out this was due to a compose window that I'd started on, started to attach a document; then went off to verify the document's latest version was saved.  When I came back to CM, I did it by raising the main window and the compose/attach windows were now hidden.

See bug 2853

Note You need to log in before you can comment on or make changes to this bug.