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 702721 - another 15+ second hang ...
another 15+ second hang ...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 712591 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-06-20 09:28 UTC by Michael Meeks
Modified: 2021-05-19 12:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Meeks 2013-06-20 09:28:40 UTC 
Milan mentioned he'd like these filed - after fetching / filtering mail from IMAP -> my local accounts I typically get a long hang; last I looked it was counting unread mail in folders; this time it was:

+ Trace 232117

Thread 486 (Thread 0x99dffb40 (LWP 25908))

  • #0 fsync
    at ../sysdeps/unix/syscall-template.S line 81
  • #1 full_fsync
    from /usr/lib/libsqlite3.so.0
  • #2 unixSync
    from /usr/lib/libsqlite3.so.0
  • #3 call_old_file_Sync
    at camel-db.c line 68
  • #4 sync_request_thread_cb
    at camel-db.c line 94
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #6 g_thread_proxy
    at gthread.c line 798
  • #7 start_thread
    at pthread_create.c line 308
  • #8 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 131 

all other threads quiescent. I guess it is other g_idle_dispatch'ed task that takes an unfeasibly long time :-)

quite possibly that is because the fsync above is hammering the system (or something), having said that I'm using ext4 which should not flush the whole filesystem if you fsync one file like ext3 did so ... ;-)

HTH.
Comment 1 Matthew Barnes 2013-06-20 12:49:51 UTC 
This is a fairly large problem to tackle.

We basically need to quit calling SQLite functions from the main thread, which happens frequently through CamelFolderSummary.  But it's going to require a good deal of API rework on the order of magnitude similar to when I added an async API to Camel itself.

It's on my To-Do list, but not something I'll be getting to before 3.10.
Comment 2 Milan Crha 2013-11-21 10:39:30 UTC 
*** Bug 712591 has been marked as a duplicate of this bug. ***
Comment 3 Milan Crha 2013-11-21 13:45:41 UTC 
Hmm, I see one related change, from bug #688926, but it's around 3.7.3, thus
part of 3.8.5, about which the bug #712591 is. Maybe there are more things
here.
Comment 4 André Klapper 2021-05-19 12:13:26 UTC 
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new bug report ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.