Created attachment 122464 [details] My kritacrash.log file, though, after searching it for dates, it's not captured these events. Some are from OpenGL crashes other may be of use in this matter. SUMMARY Krita Crashes When Closing a .kra File STEPS TO REPRODUCE 1. Open Krita 2. Load or create a .kra file. 3. Close said file. 4. Krita stops responding then crashes/closes. OBSERVED RESULT After clicking the close button for a document, Krita stops responding then crashes/closes with the document. No work is lost as long as I save before closing a .kra file. EXPECTED RESULT I expect the file to close and Krita to stay running. SOFTWARE/OS VERSIONS Windows: Windows 10 Home 64 bit macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: Unknown KDE Frameworks Version: Unknown Qt Version: Unknown ADDITIONAL INFORMATION MY SYSTEM INFORMATION: OS Name Microsoft Windows 10 Home Version 10.0.18362 Build 18362 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name TARDISWHAT System Manufacturer Dell Inc. System Model Inspiron 560 System Type x64-based PC System SKU 0 Processor Pentium(R) Dual-Core CPU E5700 @ 3.00GHz, 3003 Mhz, 2 Core(s), 2 Logical Processor(s) BIOS Version/Date Dell Inc. A06, 12/1/2010 SMBIOS Version 2.6 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer Dell Inc. BaseBoard Product 018D1Y BaseBoard Version A00 Platform Role Desktop Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "10.0.18362.267" User Name TARDISWHAT\TriXteR WHO Time Zone Central Daylight Time Installed Physical Memory (RAM) 4.00 GB Total Physical Memory 3.96 GB Available Physical Memory 409 MB Total Virtual Memory 9.34 GB Available Virtual Memory 3.58 GB Page File Space 5.38 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions No Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes
Hi, I'm sorry, but I cannot reproduce this myself. * Could you check whether this still happens if you switch Krita's renderer to Angle? (Settings->configure Krita->display). * Could you also attach the krita.log file?
Created attachment 122472 [details] krita.log Krita was already set to Angle. Here is a copy of the krita.log file.
(In reply to Boudewijn Rempt from comment #1) > Hi, > > I'm sorry, but I cannot reproduce this myself. > > * Could you check whether this still happens if you switch Krita's renderer > to Angle? (Settings->configure Krita->display). > * Could you also attach the krita.log file? I was trying to reply and add the requested file but it seems that you cannot add a file through the "reply" feature. Again, Angle was automatically selected and in the krita.log file is attached to my above comment. Apologies if this reply was unnecessary, I'm inexperienced with using forums.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
You're welcome! Check. That's good to know. Thank you for your assistance in getting this bug properly reported.
Created attachment 122501 [details] Updated Krita kritacrash.log file This "bug" still persists and an additional crash occurred. This additional crash made all the menu and tool areas disappear. I was working on the file for some time and had used the Tab key to switch to the "full-screen" mode and back several times. I think I may have added and/or moved dockers. But I no idea what it was that may have caused this second crash and the areas to disappear. It took running a portable version of the 64-bit 4.2.0 to get those back. I downloaded and ran the portable 64-bit 4.2.5 and the original crash occurred when closing a file from within that version of Krita. I downloaded and ran the 32 bit 4.2.5 and was able to load and close documents without Krita crashing. Though it did become unresponsive for a few brief moments when loading the files. But there were no issues closing them even when having three documents open to see if the crash would occur with multiple documents. These issues with the 64-bit versions of Krita have made them unusable to me. My original goal with Krita was to learn something about digital painting and to approximate Bob Ross' painting style as something constructive I can do with my time that may well also be therapeutic regarding my mental health issues. Therefore, I have switched to the 32-bit portable version to continue my endeavors with Krita. So, I am not sure what further use I can be to the developers/debuggers. However, I do hope that the next release of the 64-bit version of Krita is stable on my system. I was looking forward to exploring that version given it's designed to work on 64-bit systems such as mine and I understand it has some functionality that the 32-bit version does not. That is why I will also include an updated krita.log file as an additional attachment to aid in the refining/debugging of Krita.
Created attachment 122502 [details] Updated krita.log file Updated krita.log file showing Krita's use after the original upload of that file.
Looking at the crash log, there are several crashes that happen in the PDF import module; it might be worth while sharing the PDF file that this happens with. Some other crashes happen in the Intel GPU driver. Those should go away if you switch Krita to use Angle instead of OpenGL in settings/configure krita/display. It might also be useful to try with a clean config (see https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration)
It looks like on the reporter's system Angle is not supported. It supports only OpenGL 2.1, which is used by Krita
Hi, TrXteRWHO! Could you try to go to Preferences->Display and try to select "Software Renderer"? It looks like there is some bug in the GPU drivers that prevents Krita from functioning normally. So, bascially, you have two options: 1) Activate "Software Renderer" as a renderering engine 2) Disable Canvas Graphics Acceleration completely. Both solutions will transfer calculations from GPU to CPU, which might make Krita a bit slower, but it least it will workaround faulty GPU drivers.
(In reply to Dmitry Kazakov from comment #10) > Hi, TrXteRWHO! > > Could you try to go to Preferences->Display and try to select "Software > Renderer"? > > It looks like there is some bug in the GPU drivers that prevents Krita from > functioning normally. So, bascially, you have two options: > > 1) Activate "Software Renderer" as a renderering engine > 2) Disable Canvas Graphics Acceleration completely. > > Both solutions will transfer calculations from GPU to CPU, which might make > Krita a bit slower, but it least it will workaround faulty GPU drivers. Apologies for taking so long to get back to this thread, Boudewijn and Dmitry. I've had other matters that required my attention. Though, I am happy to report that the issue is resolved. Long story short, completely disabling the Canvas Graphics Acceleration resolved this issue. It also resolved the instability Krita 64-bit began to suffer from that forced me to switch to the 32-bit version. Short story long, over the weekend I tried a few times to uninstall Krita with RevoUnistaller and IOBit's uninstaller to see if that might resolve the issue. (This also involved changing and deleting some copies of the kritarc file. I still encountered the same problem with the 64-bit. Finally, I decided to uninstalled Krita 64-bit with one of the two abovementioned uninstallers. Then, I removed all the files Krita stores in the %LocalAppData% folder and stored those in a folder on my desktop. I cannot remember if I moved those file before or after reinstalling Krita 64-bit. But I know they were moved prior to starting Krita 64-bit for the first time. Unbeknownst to me, Krita automatically turned off the Canvas Graphics Acceleration. Since this latest installation, Krita is working as expected. I can close documents without it crashing, and they close right away without any lag or unresponsiveness. I went ahead and created two sample .kra files to see if that might cause a crash, just to be safe. Other than a slight lag after clicking the Create button when making these A4 300ppi files, I experienced no issues. Also, if I recall correctly, after the final install I did a substantial amount of work on a file with no issues. Overall, the software seems to work as designed given what features I have used to this point. In fact, it is working much better than prior to this display change. I even went ahead and installed the 4.2.6 to see if it would work properly. Work properly it did. It seems that having previously installed different iterations of both the 32-bit and 64-bit version of Krita lead the 4.2.5 version to incorrectly turn on the Canvas Acceleration. Though, it seems like this might be a bit of an ID10T error given my sloppy computer housekeeping. I'm going to attach all the files from my %LocalAppData% that I removed. I will also include the current Krita files from that said folder. I appreciate everyone's time helping me with this issue and I hope this report can help with the development of future iterations.
Created attachment 122584 [details] Updated krita.log from before uninstall Last version of the krita.log before uninstalling Krita and moving the %LocalAppData% files
Created attachment 122585 [details] Updated kritacrash.log from before uninstall Last version of the kritacrash.log before uninstalling Krita and moving the %LocalAppData% files
Created attachment 122586 [details] Old kritadisplayrc from before uninstall Last version of the kritadisplayrc before uninstalling Krita and moving the %LocalAppData% files
Created attachment 122587 [details] This kritarc file was the original and existed when this issue started. First version of the kritarc that I changed the name of while trying to troubleshoot this issue. This file is before uninstalling Krita and moving the %LocalAppData% files
Created attachment 122588 [details] A subsequent version of the kritarc file created during troubleshooting Another version of the kritarc that I changed the name of while trying to troubleshoot this issue. This file is before uninstalling Krita and moving the %LocalAppData% files
Created attachment 122589 [details] Old krita-scripterrc from before uninstall This file is from before uninstalling Krita and moving the %LocalAppData% files.
Created attachment 122590 [details] Old kritashortcutsrc from before uninstall This file is from before uninstalling Krita and moving the %LocalAppData% files.
Created attachment 122591 [details] New krita.log file created with last install/first use This was created after having moved the original krita.log file out of the %LocalAppData% folder.
Created attachment 122592 [details] New kritarc file created with last install/first use This was created after having moved the original kritarc file out of the %LocalAppData% folder.
Created attachment 122593 [details] New kritadisplayrc file created with last install/first use This was created after having moved the original kritadisplayrc file out of the %LocalAppData% folder.
Come to find out, there is no kritacrash.log file currently in the %LocalAppData% folder. This folder also lacks the kritashortscutrc and kritascripterrc files. Also, my apologies for flooding everyone's inboxes with emails and/or flooding their devices/machines with notifications regarding the uploads. I didn't think about that until after I was done with the uploads.
And, I just noticed all the comments added to the thread with each upload. :( My bad...
Hi, Sorry for missing your replies to this report. We're getting a bit swamped by our bug tracker. In any case, I understand that your issue is resolved?