Bug 335711 - High cpu usage when transfering files to smb share
Summary: High cpu usage when transfering files to smb share
Status: RESOLVED FIXED
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-02 18:53 UTC by lman
Modified: 2021-03-11 05:41 UTC (History)
2 users (show)

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

Attachments
Top app screenshot that shows the high cpu usage caused by kwalletd (55.91 KB, image/png)
2014-06-02 18:53 UTC, lman 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description lman 2014-06-02 18:53:04 UTC 
Created attachment 86970 [details]
Top app screenshot that shows the high cpu usage caused by kwalletd

For some reason kwalletd uses a lot of cpu when files are transfered to smb share (using the kio_smb).
I have only one ftp account configured in kwallet so it should not affect the files transfer to smb share (that does not require login). See the attached screenshot from top app.
Comment 1 Christian Schuhegger 2014-10-04 11:26:11 UTC 
I have the same problem.
Is there a workaround?
Comment 2 milasudril 2015-10-08 06:42:00 UTC 
(In reply to lman from comment #0)
> Created attachment 86970 [details]
> Top app screenshot that shows the high cpu usage caused by kwalletd
> 
> For some reason kwalletd uses a lot of cpu when files are transfered to smb
> share (using the kio_smb).
> I have only one ftp account configured in kwallet so it should not affect
> the files transfer to smb share (that does not require login). See the
> attached screenshot from top app.
The bug affects me too.
Comment 3 Valentin Rusu 2015-10-10 16:50:29 UTC 
Martin, any idea of why plasma calls kwallet so intensely during file copy operations?
Comment 4 Justin Zobel 2021-03-10 00:32:37 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 5 Christian Schuhegger 2021-03-11 05:41:09 UTC 
(In reply to Christian.Schuhegger from comment #1)
> I have the same problem.
> Is there a workaround?

I did not observe the problem any longer, but currently I don't use SMB either.