Bug 292619 - Sending an email makes KMail unresponsive for 5+ seconds
Summary: Sending an email makes KMail unresponsive for 5+ seconds
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-27 18:12 UTC by Davor Cubranic
Modified: 2017-01-07 22:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Davor Cubranic 2012-01-27 18:12:54 UTC
KMail 4.7.4 on KUbuntu 11.10 (Oneiric)

When I send an email, I get a "successfully sent" notification within a second or so, but then the composer window becomes a gray square and KMail is completely unresponsive for 5 seconds or more. Eventually, the main window is repainted and the application starts processing events again. During this time, I do not see any disk activity.
Comment 1 Davor Cubranic 2012-01-27 19:24:21 UTC
Even closing a composer window, choosing Discard in the warning dialog, shows the same behaviour. If anything, it takes even longer, 8-10 seconds in my tests. Shouldn't this be a zero-work op? Nothing needs to be saved or indexed.

To replicate:

1. Ctrl-N to start writing a new message
2. enter random text in the body of the message
3. click the window close button
4. choose 'Discard' in the warning dialog
5. observe 10s delay before KMail becomes interactive again.
Comment 2 Davor Cubranic 2012-01-30 21:37:32 UTC
During the delay, I can see in 'top' the kmail process running at 90% CPU.
Comment 3 Denis Kurz 2016-09-24 18:19:55 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:11:46 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.