https://bugs.kde.org/show_bug.cgi?id=491701
--- Comment #6 from bugalt29...@gmail.com --- Created attachment 172844 --> https://bugs.kde.org/attachment.cgi?id=172844&action=edit New information since previous krita.log I have been (and continue to be) very busy, however, I felt it necessary to mention that I gathered some new information during the previous week. Specifically - after switching to the OpenGL renderer, I experienced no issues related to Krita, over the span of multiple hours-long sessions over multiple days. I should note that during nearly all of my newer sessions, I was editing a different (new) file than the ones I had been editing previously (in my initial crash report). Also, all references to memory/RAM usage in the following comment are referring to the program (Krita)'s RAM usage as shown by the Windows Task Manager; not Krita's built-in memory footer. After switching back to ANGLE (the default) again, I had another instance of exponentially increasing RAM usage, followed by a soft-crash, where the canvas and most of the editor itself did not respond or refresh despite my inputs, causing the program to be unusable, and requiring me to close the program myself and restart it (after which it functioned normally again). Over several sessions and multiple days, I monitored the RAM usage rates when OpenGL or ANGLE were selected to get an idea of a typical usage rate for each of them. For OpenGL, I believe the number was between 200-700 megabytes, and never exceeded 1 gigabyte (at least, for the file I was editing). For ANGLE, the number was somewhere around the 0.7-1.5 gigabytes range, on average (which is entirely acceptable). There was one exception, however (explained below). When Krita soft-crashed this time (while using the ANGLE renderer, same as my original crash report), I had been observing Krita's RAM usage using Windows' Resource Monitor over time (prior to it soft-crashing) and noticed it had been strangely increasing in RAM despite the file being edited not having very major changes made to it during the same timeframe; nor did RAM usage ever increase in a similar manner when the OpenGL renderer was selected instead of ANGLE. During the soft-crash, Krita had reached over 8 gigabytes of working memory. As before, and as you've mentioned, I am unsure if memory is at all related to the crashes, but it appeared to be abnormal, and coincided almost perfectly with several of the aforementioned crashes as well, so I am including it as it may be potentially insightful. Because the program did not hard crash, and was manually closed by me instead, my kritacrash.log file did not update to include any new crash information compared to the one I already uploaded. The soft-crash occurred sometime around 2:00 PM (14:00) on August 17th. I have a recording of it which showed its symptoms and Resource Monitor usage as it was occurring, however, I have not yet edited my personal information (which was accidentally displayed on-screen) out of the recording yet, and the recording also contains potentially offensive content (a cartoon character dead by hanging, drawn as part of a comic). If such a recording would be both potentially useful and acceptable for me to upload as an attachment (after I find the time to remove my personal information from it) please let me know, and I could upload it. -- You are receiving this mail because: You are watching all bug changes.
