Bug 317869 - Composer attach file manager very slow in directory containing ssl-certificates
Summary: Composer attach file manager very slow in directory containing ssl-certificates
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-05 10:20 UTC by dorfl
Modified: 2017-01-07 22:41 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description dorfl 2013-04-05 10:20:15 UTC 
The file manager is very slow when I try to attach one (or multiple) files in a directory containing a lot of ssl-certificates (in my case 168 pem-files with associated keys, csr and 58 pkcs12 editions of some certificates). The kmail-process also uses well over 90% of the cpu during the attach.

Reproducible: Always

Steps to Reproduce:
1. New Message
2. Attach
3. Go to catalog containing many ssl-certificates (168 in my case).
Actual Results:  
The whole file manager responds very slowly. Searching, dragging toolbars and selecting files responds very slow.

Expected Results:  
Fast response like I get in catalogs without ssl-certificates.
Comment 1 Laurent Montel 2013-04-05 11:50:51 UTC 
which size directory size ?
Comment 2 dorfl 2013-04-07 15:39:43 UTC 
Directory size is 3.9M.
Comment 3 dorfl 2013-04-07 15:40:38 UTC 
(In reply to comment #1)
> which size directory size ?

Directory size is 3.9M
Comment 4 Denis Kurz 2016-09-24 18:22:38 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 5 Denis Kurz 2017-01-07 22:41:19 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.