https://bugs.kde.org/show_bug.cgi?id=430458
Halla Rempt changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=430458
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=430458
--- Comment #6 from Denys Motornyi ---
Hmm.. ok, it makes sense. Except that I though I only have what comes with the
default Krita installation, and nothing additional. I'll doublecheck, maybe
somehow something has left over from older installations.
https://bugs.kde.org/show_bug.cgi?id=430458
--- Comment #5 from Halla Rempt ---
Do you have a really large amount of resources, like brush presets or patterns
or things like that installed? Krita 4 loads all resources into memory
(something we've already changed for what will become Krita 5),
https://bugs.kde.org/show_bug.cgi?id=430458
--- Comment #4 from Denys Motornyi ---
Ok, it appears there is something else. I cannot reproduce the crash anymore.
What I still face is that the memory usage is really high. While Krita loads
the image, the peak is around 22Gb according to they
https://bugs.kde.org/show_bug.cgi?id=430458
Halla Rempt changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Component|File formats
https://bugs.kde.org/show_bug.cgi?id=430458
--- Comment #2 from Halla Rempt ---
Oh, and the image is actually RGBA, so the expected memory consumption would be
36 bytes (because there's only one layer, the projection is shared with
the layer itself) -- which is more or less what we see.
https://bugs.kde.org/show_bug.cgi?id=430458
Halla Rempt changed:
What|Removed |Added
CC||b...@valdyas.org
--- Comment #1 from Halla Rempt
