SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE Cannot do so reliably. Once it was setting a gaussian blur on a layer, another time it was selecting a brush. Seems random. Basically, try to use Krita to do basic digital painting. After about 10-15 minutes, it will crash. One time it was after about 3 minutes. OBSERVED RESULT Graphics drivers crash with varying severity. In all cases the monitor running Krita goes black and loses input signal for a bit. Sometimes I can get it to come back. Krita is white in those cases, but can be killed without issue from the task bar. ** I believe it is the AMD crash guard that is preventing a worse crash, but not certain. One time both monitors lost all signal and I had to hard reboot my machine to restart it. EXPECTED RESULT Krita works without crashing my graphics drivers SOFTWARE/OS VERSIONS Windows: 11 Pro macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION System specs: Alienware rig, in case that matters AMD Ryzen 9 5900 processor 32 GB RAM AMD Radeon RX 6900 XT graphics card Running two monitors, one using a DisplayPort and the other HDMI. Displayport monitor is the primary one, and usually what Krita is running on. No crash reports available, I'm afraid. The program itself does not seem to crash, just all ability to actually see it.
Um, we cannot do much about broken graphics drivers? You can try to switch between Angle and OpenGL in Krita and see if that makes a difference, or make sure the drivers are up to date.
(In reply to Halla Rempt from comment #1) > Um, we cannot do much about broken graphics drivers? You can try to switch > between Angle and OpenGL in Krita and see if that makes a difference, or > make sure the drivers are up to date. Hmm, I'll try that and see if it works. Drivers are up to date, so not much more I can do, I think. I know you can't do anything about a bug in the drivers themselves, but it seemed worth reporting in case there is something funky going on in the Krita code that could cause it. The fact that it only happens with Krita, and literally no other program on my machine, means that is at least possible. Something to watch out for in case you get further reports, at least.
What other applications that use opengl do you use?
(In reply to Halla Rempt from comment #3) > What other applications that use opengl do you use? That's a good question, actually. I think there are several games that I play that use it, but I'll have to verify that. I will find one of them that I can verify uses opengl and see if I that causes similar issues.
Most windows games will use d3d (which we use instead of the opengl drivers if angle is enabled). In gneeral, the opengl drivers are much, much worse than the d3d drivers on Windows.
Good to know. I'll see if what you have told me can help me track down the source of this issue. It would be nice to be able to actually use Krita on this computer!
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.
Setting this back to needsinfo until David can pin down whether other programs on their device do the same.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!