After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 248353 - Composer autosave should run in another thread
Composer autosave should run in another thread
Status: RESOLVED DUPLICATE of bug 590747
Product: evolution
Classification: Applications
Component: Mailer
pre-1.5 (obsolete)
Other All
: Low normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer]
Depends on:
Blocks:
 
 
Reported: 2003-09-10 16:51 UTC by Rodney Dawes
Modified: 2009-09-23 13:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rodney Dawes 2003-09-10 16:51:16 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...

  • #0 poll
    from /lib/libc.so.6
  • #1 send_dg
    from /lib/libresolv.so.2
  • #2 __res_nsend
    from /lib/libresolv.so.2
  • #3 __res_nquery
    from /lib/libresolv.so.2
  • #4 __res_nquerydomain
    from /lib/libresolv.so.2
  • #5 __res_nsearch
    from /lib/libresolv.so.2
  • #6 _nss_dns_gethostbyname2_r
    from /lib/libnss_dns.so.2
  • #7 gethostbyname2_r
    from /lib/libc.so.6
  • #8 gaih_inet
    from /lib/libc.so.6
  • #9 getaddrinfo
    from /lib/libc.so.6
  • #10 e_gethostbyname_r
  • #11 get_hostbyname
    at camel-service.c line 710
  • #12 camel_gethostbyname
    at camel-service.c line 762
  • #13 header_msgid_generate
    at camel-mime-utils.c line 3799
  • #14 camel_mime_message_set_message_id
    at camel-mime-message.c line 262
  • #15 write_to_stream
    at camel-mime-message.c line 508
  • #16 camel_data_wrapper_write_to_stream
    at camel-data-wrapper.c line 164
  • #17 autosave_save_draft
    at e-msg-composer.c line 1300
  • #18 g_hash_table_foreach
    at ghash.c line 559
  • #19 autosave_run
    at e-msg-composer.c line 1438
  • #20 g_timeout_dispatch
    at gmain.c line 3124
  • #21 g_main_dispatch
    at gmain.c line 1751
  • #22 g_main_context_dispatch
    at gmain.c line 2299
  • #23 g_main_context_iterate
    at gmain.c line 2380
  • #24 g_main_loop_run
    at gmain.c line 2600
  • #25 bonobo_main
    at bonobo-main.c line 294
  • #26 main
    at main.c line 637
  • #27 __libc_start_main
    from /lib/libc.so.6

Comment 1 Not Zed 2003-09-23 00:25:13 UTC
This is really a local configuration issue, since hostnmae lookups
aren't working.

But this should really be done in another thread too.
Comment 2 André Klapper 2005-02-09 17:34:38 UTC
adding performance keyword
Comment 3 Karsten Bräckelmann 2006-03-30 13:11:49 UTC
I couldn't agree more with NotZed... :)
Comment 4 Johnny Proton 2009-09-23 13:09:26 UTC
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.
Comment 5 Johnny Proton 2009-09-23 13:18:06 UTC
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.
Comment 6 Milan Crha 2009-09-23 13:38:05 UTC
Actual master (2.29.1 material) seems to do this in another thread, even waiting for the folder opening. Saving itself is done asynchronously.
Comment 7 Matthew Barnes 2009-09-23 13:50:53 UTC

*** This bug has been marked as a duplicate of bug 590747 ***