GNOME Bugzilla – Bug 248353
Composer autosave should run in another thread
Last modified: 2009-09-23 13:50:53 UTC
After I got to work today, I went to compose some e-mail and the composer started blocking randomly while writing the message. A backtrace seems to indicate that it's blocking on looking up the hostname for my machine...
+ Trace 40083
This is really a local configuration issue, since hostnmae lookups aren't working. But this should really be done in another thread too.
adding performance keyword
I couldn't agree more with NotZed... :)
I am in Fedora 11 X86-64 and I see this behaviour CONSTANTLY. I can't tell why it's doing it, but Evolution freezes for maybe 5 seconds, then comes back again. I did notice that I had about 6 composer emails open and yes, these emails would have been auto-saved to the IMAP store which would be dependent upon the network. My Comcast seems to have quite a latency on ping so I wonder if it was freezing because of the composer windows. Finally, I just wrote all the emails and now evolution isn't hanging. Although when you are not writing any emails, it is kind of pointless.
I also did make the behaviour stop by changing my "Drafts" location to a local folder, instead of the IMAP folder. Fixing this bug would make this problem go away entirely though. Better to have the drafts on the IMAP store, if you are an IMAP user.
Actual master (2.29.1 material) seems to do this in another thread, even waiting for the folder opening. Saving itself is done asynchronously.
*** This bug has been marked as a duplicate of bug 590747 ***