Bug 243043 - High memory load under normal usage
Summary: High memory load under normal usage
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 2.1
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-28 16:22 UTC by Leonardo La Malfa
Modified: 2010-08-30 16:41 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot (426.36 KB, image/png)
2010-06-28 16:22 UTC, Leonardo La Malfa
Details
Screenshots 1 of 2 (763.02 KB, application/octet-stream)
2010-06-30 17:57 UTC, Leonardo La Malfa
Details
Screenshots 2 of 2 (825.60 KB, application/octet-stream)
2010-06-30 17:58 UTC, Leonardo La Malfa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo La Malfa 2010-06-28 16:22:53 UTC
Created attachment 48424 [details]
Screenshot

Version:           2.1 (using KDE 4.4.4) 
OS:                Linux

For some reason, the Web site doesn't let me choose the correct version, but I'm using 2.2.0. I don't know how to make this report more useful, but here goes: after 30 minutes of testing every menu and several options of Krita, I checked System Monitor, and saw the application was using 983 M (please, see screenshot attached), 200 M short of using all available RAM. Is it a problem of memory leaking? Please, let me know if I can help with more details next time.

Reproducible: Always




OS: Linux (i686) release 2.6.32-22-generic
Compiler: cc
Comment 1 Sven Langkamp 2010-06-30 15:14:31 UTC
It would be great if you could find out after which operation the memory usages increases.
Comment 2 Leonardo La Malfa 2010-06-30 17:57:37 UTC
Created attachment 48489 [details]
Screenshots 1 of 2

On Wednesday 30 June 2010 15:14:33 Sven Langkamp wrote:
> It would be great if you could find out after which operation
> the memory usages increases.

Sure thing! I used Krita for an hour this afternoon, and documented with some screenshot as I tested different tools, and this is what I found out:

- if I start by opening last project (the drawing that can be seen in the screenshot uploaded while opening this bug report), totalling 6,8 MiB, then Krita RAM usage starts already from 245 M;
- if I start a new project, Krita starts from around 63 M - I chose this option;
- I started with Dyna brush, but 2 minutes later it already added 100 M, now totalling 163 M (see Screenshot1)
- Deform brush takes a lot of CPU, but not much RAM;
- I just changed to Curve brush and chose a different colour (yellow) and started painting around the center for 30 seconds, and RAM jumped to 373 M (see Screenshot2);
- Pixel brush + Dynamic movements didn't increase RAM significantly;
- Stars shape + Deform brush didn't affect RAM much, nor did Stars + Chalk;
- Spray brush + Dynamic movements does increase RAM (the higher the number of particles, the quicker RAM raises), and if movements are too quick then CPU usage gets too high, and window freezes until all particles have settled (see Screenshot3);
- Drawing paths did increase RAM (see Screenshot4);
- Grid brush + Shapes (straight lines + ellipses) didn't affect RAM;
- most filters I've tested (oilpaint, desaturate, blur, color to aplha and color transfer, sharpen and emboss) didn't affect RAM, on the contrary, after an initial surge of 100 M+, they usually drop to values lower than initial ones (around 5 M less each);
- tried Spray brush + Dynamic movements again increasing number of particles: it did increase RAM again, and I saw that the higher the number of particles, the quicker RAM raises (see Screenshot5);
- I remembered that Particle brush did increase RAM, but looking at Screenshot6 it seems it did not, after all.

Screenshots are split in two compressed files for size limit reasons. This is by no means an exhaustive test, but I hope you will find the results useful somehow. Many thanks!
Comment 3 Leonardo La Malfa 2010-06-30 17:58:51 UTC
Created attachment 48490 [details]
Screenshots 2 of 2
Comment 4 Halla Rempt 2010-06-30 19:36:04 UTC
Thank you! These are very useful observations!
Comment 5 Halla Rempt 2010-08-11 22:34:36 UTC
BUGDAY
Comment 6 George Goldberg 2010-08-22 22:45:59 UTC
I followed through the steps in comment #3 and saw no significant memory consumption increase for any of them (Krita trunk and Intel graphics). Might be graphics card/driver related?
Comment 7 Kubuntiac 2010-08-22 23:05:46 UTC
When I follow the instructions above that got Leonardo's Krita using 373mb,
mine uses 83mb.

Opening a new (1024x768 RGB) image uses 55mb
Dyna draw went to 72mb
Curve brush draw (in Yellow :o) went to 83mb.

So....

Can't confirm.

TECH SPECS:
Krita revision 1166713
Kubuntu 10.04 32bit
KDE 4.5
QT 4.7.0 beta 2
ATI Radeon x1250 with FOSS ATI driver v6.13.0
Comment 8 Leonardo La Malfa 2010-08-22 23:13:18 UTC
> Might be graphics card/driver related?

It might. I have an ATI Radeon HD 3450, and when I tested Krita for the bug report I was using the open source driver. As a test, I've switched to the proprietary FGLRX graphics driver tested by the Ubuntu developers (available in Jockey), and gave Krita 2.2.1 another try. The steps mentioned above resulted in the same increase of RAM. It's got to be me.
Comment 9 Cyrille Berger 2010-08-23 10:31:08 UTC
It is also possible that the bug got fixed in krita/trunk (upcoming 2.3).
Comment 10 LukasT 2010-08-26 09:24:04 UTC
I think so too. Dmitry fixed problem with recreating the KisPaintDevices, which are recreated in the paintops mentioned in the report. I guess this is fixed in trunk. I can't reproduce it
Comment 11 Halla Rempt 2010-08-30 16:41:59 UTC
Fixed in trunk :-)