Bug 153795 - absurd amount of syscalls to check local mail
Summary: absurd amount of syscalls to check local mail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-10 19:33 UTC by Manuel Amador (Rudd-O)
Modified: 2018-09-04 18:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
ridiculously long strace dump (129.16 KB, text/plain)
2007-12-10 19:34 UTC, Manuel Amador (Rudd-O)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Manuel Amador (Rudd-O) 2007-12-10 19:33:36 UTC
Version:            (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

I'm attaching a small 5-second strace where kmail is absurdly statting and accessing /usr/share/* a bunch of .mo message files for no reason while retrieving local mail from /var/mail/username.

Kmail freezes completely during that local mail check.
Comment 1 Manuel Amador (Rudd-O) 2007-12-10 19:34:44 UTC
Created attachment 22460 [details]
ridiculously long strace dump
Comment 2 Bram Schoenmakers 2007-12-10 21:47:33 UTC
I don't see these access() calls when doing a check on a local maildir.
Comment 3 Thomas McGuire 2007-12-15 18:49:59 UTC
This might be a distribution problem, the file /usr/share/i18n/charmaps/ANSI_X3 doesn't seem to exist on your system.
Not sure where the call comes from, though.
Comment 4 Björn Ruberg 2010-01-14 01:08:12 UTC
Is this still a problem?
Comment 5 Manuel Amador (Rudd-O) 2010-01-14 01:26:05 UTC
I donno.  I would have to test.

You should know that the freeze happens only with ZFS-FUSE as a filesystem operating /usr.  Or any other FUSE filesystem.  Because storms of VFS syscalls usually cause processes to freeze when any FUSE filesystem is serving them.  Thus making FUSE filesystems ideal tools to figure out when processes are doing *abusive* things like KMail does in this case.
Comment 6 Björn Ruberg 2010-01-14 01:39:30 UTC
It would be great if you can look into this again. Thomas called this a possible distribution problem - if it was that, it may be fixed now. The chance that a developer looks into this will increase if you can provide the latest data. Of course, there are many many bugs open, so noone can guarantee - but if there is too much work done here solving this maybe a simple way to improve performance
Comment 7 Andrew Crouthamel 2018-09-04 18:18:17 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!