Summary: | Crash on opening any file | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | 7.7meter |
Component: | OpenGL Canvas | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | gamedj2015, halla |
Priority: | NOR | ||
Version: | 3.1.2 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: |
Description
7.7meter
2017-02-02 16:05:04 UTC
Hi, I guess you could workaround this crash by disabling opengl -- it clearly happens right inside the intel display driver: krita.exe caused an Access Violation at location 00007FFE74B042E4 in module ig75icd64.dll Reading from location 0000000000000008. It isn't the first problem we have with intel drivers -- black screens, canvas doesn't update until some gui element is selected, and now a crash again. Intel guys, you should check pointers before reading pointers! Without an actual test system this is going to be really hard to debug. We're obviously doing something the intel driver developers have never expected, but we're still using opengl correctly, as far as we know... (In reply to Boudewijn Rempt from comment #1) > Hi, > > I guess you could workaround this crash by disabling opengl -- it clearly > happens right inside the intel display driver: > > krita.exe caused an Access Violation at location 00007FFE74B042E4 in module > ig75icd64.dll Reading from location 0000000000000008. > > It isn't the first problem we have with intel drivers -- black screens, > canvas doesn't update until some gui element is selected, and now a crash > again. Intel guys, you should check pointers before reading pointers! > > Without an actual test system this is going to be really hard to debug. > We're obviously doing something the intel driver developers have never > expected, but we're still using opengl correctly, as far as we know... Thank you, disabling opengl solved the problem (and now I am getting less brush lag). I still wish I could figure out exactly _why_ this crash happens. I'll mail my Intel contact tomorrow. Confirming, a crash with backtrace is always confirmed -- even if the crash might not be in krita itself... (In reply to Boudewijn Rempt from comment #3) > I still wish I could figure out exactly _why_ this crash happens. I'll mail > my Intel contact tomorrow. UPDATE: I managed to fix the problem by removing the OEM provided driver and installing the latest from intel. The wrong version was 10.18.10.3740 (or something like that, I do not know how Fujitsu has tampered with it), the current working version is 10.18.14.4578. Ah, thanks for the information! Then we can close as upstream.... *** Bug 376006 has been marked as a duplicate of this bug. *** |