https://bugs.kde.org/show_bug.cgi?id=456998
Tiar changed:
What|Removed |Added
Keywords||triaged
CC|
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #19 from Dmitry Kazakov ---
Hi, Ralek!
Thanks for your detailed reply! The videos give a very little, but still some
clues :) I will think about that in the background, perhaps I'll get some
ideas.
The video shows that the problem is not
https://bugs.kde.org/show_bug.cgi?id=456998
Halla Rempt changed:
What|Removed |Added
Status|REPORTED|ASSIGNED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #18 from Ralek Kolemios ---
Created attachment 151084
--> https://bugs.kde.org/attachment.cgi?id=151084=edit
Standard stroke completion
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #17 from Ralek Kolemios ---
Created attachment 151083
--> https://bugs.kde.org/attachment.cgi?id=151083=edit
Slow stroke completion
> Do I understand that correctly, if you just load a lot of documents that
> occupy 30GiB of RAM, Krita
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #16 from Dmitry Kazakov ---
And one more test, sorry :)
1) Go to Krita settings, Performance and set "swap undo after" to some really
small value, like 50MiB
2) Restart Krita
3) Open your standard huge document
Does it look as slow and
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #15 from Dmitry Kazakov ---
And one more question :)
Could you explain in more detail, what do you mean by "sluggish"? Some specific
tools work slower? Or zooming/panning? Or menus? Perhaps you could make a video
of this state?
--
You
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #14 from Dmitry Kazakov ---
Hi, Ralek!
Could you also answer two questions:
1) What value do you have set in "Undo Limit" option?
2) What maximum size you have assigned to the swap file (on the Performance
tab)?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #13 from Dmitry Kazakov ---
> I'm not too familiar with memory leaks, if it doesn't get to the point where
> I'm running out of memory, shouldn't it theoretically not slow down?
The conventional "leak" is when an application loses
https://bugs.kde.org/show_bug.cgi?id=456998
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #11 from Ralek Kolemios ---
(In reply to Dmitry Kazakov from comment #4)
> What is the size of the image you work with? I mean, size in pixels and
> average numbel of layers?
Theyre at 16bpc, and can be anywhere from 2kx2k to 5kx5k, and
https://bugs.kde.org/show_bug.cgi?id=456998
Dmitry Kazakov changed:
What|Removed |Added
Status|ASSIGNED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #9 from Dmitry Kazakov ---
Hi, Ralek!
Could you please test tomorrow's nigtlies (either stable or master), whether
the problem still persists? I have fixed an obvious leak, but there is still an
issue of the memory pools, which are not
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #8 from Dmitry Kazakov ---
Git commit dafa966d5ac5a36eb3608d62d8f13ef4c667ca67 by Dmitry Kazakov.
Committed on 01/08/2022 at 14:23.
Pushed by dkazakov into branch 'krita/5.1'.
Fix a tiny memory leak in KisTileDataStore
The garbage
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #7 from Dmitry Kazakov ---
Git commit cf53533b1d848ababcdffdf3a5cfbb3c0dc4e881 by Dmitry Kazakov.
Committed on 01/08/2022 at 14:23.
Pushed by dkazakov into branch 'krita/5.1'.
Fix a memory leak in the storyboard caused by a strong pointer
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #6 from Dmitry Kazakov ---
Git commit 64026b836b0e456824d3a1bd644501192ad0537d by Dmitry Kazakov.
Committed on 01/08/2022 at 14:21.
Pushed by dkazakov into branch 'master'.
Fix a memory leak in the storyboard caused by a strong pointer to
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #5 from Dmitry Kazakov ---
Git commit c878c55e1c8eb626b57e0dc51432f4f4427571fa by Dmitry Kazakov.
Committed on 01/08/2022 at 14:21.
Pushed by dkazakov into branch 'master'.
Fix a tiny memory leak in KisTileDataStore
The garbage collection
https://bugs.kde.org/show_bug.cgi?id=456998
Halla Rempt changed:
What|Removed |Added
Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com
CC|
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #4 from Dmitry Kazakov ---
Hi, Ralek!
What is the size of the image you work with? I mean, size in pixels and average
numbel of layers?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #3 from Ralek Kolemios ---
(In reply to Dmitry Kazakov from comment #2)
> 1) Does the performance degradation persist if you close the document and
> reopen it **without** restarting Krita?
> 2) Does the performance degradation persist if
https://bugs.kde.org/show_bug.cgi?id=456998
Dmitry Kazakov changed:
What|Removed |Added
CC||dimul...@gmail.com
--- Comment #2 from Dmitry
https://bugs.kde.org/show_bug.cgi?id=456998
--- Comment #1 from Ralek Kolemios ---
Neglected to mention that this is not Windows 11 or 5.2 specific, I believe
this has been a problem for me for a couple years now.
--
You are receiving this mail because:
You are watching all bug changes.
22 matches
Mail list logo
