The program crashes when you press the OK button of the configuration window, if there are any documents open. I only tried it on these versions: 2.9.11 and 3.0.1.1, for Windows 64. I repeat that the same problem happens on 3.0.1.1. - The problem happens if you change or not change any configuration. - This problem does not happen if there are no documents open. If you close all documents and then open the configuration window, it does not crash when you press OK. Reproducible: Always Steps to Reproduce: 1. Open Krita; 2. Create or open a document; 3. Go to Settings -> Configure Krita; 4. Press the OK button, it crashes. Actual Results: I don't have a debug build for 2.9.11, the information in the Windows crash dialog is this: "Problem signature: Problem Event Name: APPCRASH Application Name: krita.exe Application Version: 0.0.0.0 Application Timestamp: 56b088dd Fault Module Name: QtCore4.dll Fault Module Version: 4.8.6.0 Fault Module Timestamp: 55deb63e Exception Code: c0000005 Exception Offset: 000000000011cd44 OS Version: 6.3.9600.2.0.0.768.101 Locale ID: 2057 Additional Information 1: de4a Additional Information 2: de4abe48748cb1699417715147f18589 Additional Information 3: 488b Additional Information 4: 488bb8138f271b13ca4c7e0c4dfbea1a" This happens on this system: - Windows 8.1 64; Intel i7-4720HQ; Intel HD 4600, NVIDIA GTX 960M. Drivers are updated, other OpenGL applications are working. - Fresh installation of Krita.
Hi, I'm sorry, but I cannot reproduce the issue with 3.0.1.1 on my Windows 10 laptop. Can you try to reproduce with the 3.0.1.90 debug build (http://download.kde.org/unstable/krita/3.0.1.90/krita-3.0.1.90-x64-dbg.zip) and see whether you get a backtrace? Testing with 2.9 is not useful to us, there won't be any 2.9 series releases anymore.
Hi, thank you for reviewing this. I will take a look at that debug version. Do I need to install that DrMinGW software as well? I don't have much experience with this.
Created attachment 101611 [details] Backtrace I used the instructions here: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB With the GDB from MinGW64 from here: https://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20(Win64%20hosted)/gdb/ ...to output to the attached file. I think the crash is right at the end of the file, something to do with OpenGL. The steps to crash were these: 1) Run Krita 2) Create a new document 3) Open the configuration window (Settings->Configure Krita) 4) Press the OK button.
The guidelines for Krita are here: https://docs.krita.org/KritaFAQ#How_can_I_produce_a_backtrace_on_Windows.3F But, yes, that's a crash in the Intel opengl driver. Sounds like Krita gets confused because you've got two gpu's in your system. You should tell Windows to make Krita use the nvidia gpu. It's not something we can control from within Krita.
Please tell us exactly which brand and model of system you have, and which version of Intel display chip and display driver you have? For the driver version, press the Windows key, then type "Device Manager", open the Device manager application and check the Display Adapter dialog.
My OS is Windows 8.1 64 Display: Intel HD Graphics 4600 (driver 10.18.14.4578 from 2017-01-04) NVIDIA GeForce GTX 960M (driver 10.18.13.5582 from 2015-08-25) The dates above are in the format yy-mm-dd. When I tried Krita version '3.0.1.90 debug build' the problem didn't happen, so this is inconclusive. I don't think there's an easy solution, I won't mind if you close this issue.
And does it also happen if you run krita explicitly on the nvidia gpu?
(In reply to Boudewijn Rempt from comment #7) > And does it also happen if you run krita explicitly on the nvidia gpu? Yes, running explicitly with either of the GPUs causes the problem.
I tested it today, 'Krita 3.1.3 beta 1' does not have the problem I described anymore.
Ah, good!