https://bugs.kde.org/show_bug.cgi?id=491701

            Bug ID: 491701
           Summary: Excess RAM Usage (ignores settings) and repetitive
                    crashing for unknown reason
    Classification: Applications
           Product: krita
           Version: 5.2.2
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: * Unknown
          Assignee: krita-bugs-n...@kde.org
          Reporter: bugalt29...@gmail.com
  Target Milestone: ---

Created attachment 172611
  --> https://bugs.kde.org/attachment.cgi?id=172611&action=edit
Krita crash log file

SUMMARY
I observed Krita causing slowdown and crashes several times over the past
several days for unknown reasons. RAM usage as shown by the Windows Task
Manager also exceeded the RAM limit set in Krita's Performance menu, and did
not appear to coincide with the RAM usage as reported by Krita itself (in the
bottom info bar). Despite being limited to 40% or 6.4gb (of 16gb) in the
settings, Krita was observed to consume >7.9gb of system memory before and
during at least one of its crashes. (Others not observed/confirmed.) During all
recent crashes, the file open and being edited was at or below ~400mb in size,
and Krita itself reported a similar total memory usage (<=~500mb) in the bottom
information bar when hovered over.

STEPS TO REPRODUCE
Unknown (Regular use)

OBSERVED RESULT
Excess RAM usage (up to 8gb+), computer slowdown and eventual crash. No
autosave prompt was displayed following at least one reopening.

SOFTWARE/OS VERSIONS
Windows 11 Home Version 23H2
Not related to cumulative Windows updates KB5041585 & KB5042099 released Aug 13
(I have not updated to them yet)

ADDITIONAL INFORMATION
Several of the crashes did not immediately crash the application itself, but
caused intense PC-wide slowdown (sometimes for over 10 seconds) making the
desktop completely unusable, before Krita crashed (or was force exited). The
crash log file appears to show only four crashes between Aug 12 and Aug 13,
though I believe (potentially wrongly--it's been a blur) that I had to force
close the application at least one time potentially not reported there.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to