|
|
krita-memory-display.png (36,037 bytes) |
|
|
krita-memory-warning.png (24,757 bytes) |
|
|
kunda, just keep in mind, that the amount of memory being used by a program is most of the time useless. at least, this is what i've learned by reading the recurring discussions about memory consumption in browsers. summarized: the operating system will keep on allocating memory for the software and won't ask for it to be freed, unless other programs need the memory. so, a huge memory consumption can be a good thing! and no action on your side (or the programmers side) is probably needed. if a software uses lot of memory on your computer, it does not always mean that it might need even more memory to be more performant. it might simply be that it freely keeps all memory allocated by the OS if the OS does not reclame it back... the operating system itself can show you how much memory it allocates to each running program. and i wonder if that is not more than enough... making it more prominent might lead many people to worrying about the wrong things... (and as we know, every line of code that is not written will be bug free, won't have to be maintained, and won't enhance the feeling that scirbus has a huge messy code base...) |
|
|
Kunda : imo such geeky features should not meet too much light. 'Undo', Style management or #layout bugs are so much more important ! |
|
|
apha1.png (19,152 bytes) |
|
|
ale, I'm not so sure Krita works the way you mention. I asked on #Krita and even through I didn't get a clear yes/no response, I got the sense that comparing Krita to Browsers isn't accurate. That Krita doesn't take RAM indiscriminately. jluc, it can help triage bugs better. Like if we had a debug mode setting in the GUI. Just an FYI, this issue is tagged 'Future Release' so I see no priority or anticipation that it will be implemented anytime soon...unless Franz has a moment of awesome whimsy and out of the blue decides to do it. |
|
|
We do not use our own memory allocation system so we would have no way of tracking memory usage without rewriting all of the object creation requests for all obejcts including every single QString, UI element etc. That's not going to happen. The only generic way would be to somehow query the system to get the same info that top/Task Manager produces. Not much value in spending that time when it can be gained from the system. |
|
|
Also, in a flat paint program, you have layers of canvases of a determined size, so you know how large the size of memory is, with width x height x colour depth (+ transparency). We could calculate it for all the images etc, but I don't see too much value. |
|
|
Thanks Craig for elaborating. Giving up on this feature. Resolving ticket |
- Anonymous
