Bug 348778 - High CPU Usage If Brushes Are Not Loaded
Summary: High CPU Usage If Brushes Are Not Loaded
Status: RESOLVED DUPLICATE of bug 344968
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (show other bugs)
Version: 2.9.4
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-06 07:26 UTC by Mister Glaceon
Modified: 2019-09-05 08:16 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mister Glaceon 2015-06-06 07:26:06 UTC
This is far from a fatal bug, and I'm sure it's pretty easy to miss if you guys have large screens, and don't need as many tabs as I do from this laptop. Or simply have different tab preferences from me.

For some reason, Krita uses a lot of CPU when the brushes aren't loaded for the first time in a session. All I can do is guess that it goes in a loop waiting for the brushes to load, and once you do open the brushes tab, everything's fine. CPU rapidly slides back down to 0% if you're not doing anything.

The issue is very easily reproduced, as I put down in the steps below. I've reproduced it five times in a row one night. This bug affects all 2.9 builds I have used, including the newest Windows build in the repos, 2.9.5. I was hoping it would be fixed by now, but I guess it's hard to keep tabs on every bug if it's not reported here. Nothing wrong with being organized, I say.

Reproducible: Always

Steps to Reproduce:
1. Exit Krita without the Brush tab open
2. Open Krita, and do not click on the Brushes tab right away
3. Watch as the canvas' performance suffers from 50-55%

Actual Results:  
High CPU usage, usually 50 to 55%

Expected Results:  
Idled back down to 0%, if not doing anything.
Comment 1 Halla Rempt 2015-06-06 07:41:49 UTC
Hi!

I suspect that this is another manifestation of 344968.

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