Bug 349703 - High CPU usage with multiline text
Summary: High CPU usage with multiline text
Status: RESOLVED DUPLICATE of bug 306181
Alias: None
Product: krita
Classification: Applications
Component: Tools (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-29 07:26 UTC by mvowada
Modified: 2015-08-11 10:34 UTC (History)
1 user (show)

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

Attachments
Video (1.24 MB, video/mp4)
2015-06-29 07:30 UTC, mvowada 		Details
Test with OpenGL enabled and disabled. (577.92 KB, image/png)
2015-07-01 09:23 UTC, mvowada 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description mvowada 2015-06-29 07:26:33 UTC 
I've noticed a considerable CPU usage:
A) when I type on a multiline text frame, as well as
B) when I move the multiline text frame over the canvas (please, see video below).

- Krita: 2.9.5 (git 9fe0557)
- Ubuntu 14.04 - Unity
- Core2 Quad CPU

Reproducible: Always

Steps to Reproduce:
Either case:
1. enter some multiline text
1. move a multiline text box

Actual Results:  
Considerable CPU usage and lags.

Expected Results:  
Lower CPU usage and responsiveness.

This issue has been mentioned in part also in:
- Bug 346006
- Bug 306181
Comment 1 mvowada 2015-06-29 07:30:42 UTC 
Created attachment 93394 [details]
Video
Comment 2 Halla Rempt 2015-07-01 05:44:00 UTC 
is that with opengl enabled or disabled?
Comment 3 mvowada 2015-07-01 09:23:04 UTC 
Created attachment 93444 [details]
Test with OpenGL enabled and disabled.

Hello Boudewijn,
It seems it happens in either case, that is with OpenGL enabled "AND" disabled (see PNG file in attachment).
Tested with:
- GeForce 9800 GT/PCIe/SSE2 Video card
- OpenGL version string: 3.3.0 NVIDIA 331.113
Comment 4 Halla Rempt 2015-08-11 10:34:28 UTC 
Let's track all the multiline text tool bugs in 306181 -- it needs rewriting in any case.

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