[krita] [Bug 383281] Krita on Windows 10: always crashes File > New, File > Open, File > Open Recent
https://bugs.kde.org/show_bug.cgi?id=383281 Alvin Wong changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED CC||[email protected] --- Comment #6 from Alvin Wong --- The problem is probably with inheriting from the versioned QOpenGLFunctions_x_x instead of the more flexible QOpenGLFunctions. I can see how it might be fixable, but it would need to wait at least until 3.2.1. But even then, the driver is just too old, it's so old that it's practically useless for today. I'm sure there is a "newer" one with at least OpenGL 3.0 support. (Side note: I think even ANGLE wouldn't work with this integrated graphics because it doesn't support D3D11, which actually would be a nice candidate for testing how the Qt automatic OpenGL detection choose in cases like this.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383281] Krita on Windows 10: always crashes File > New, File > Open, File > Open Recent
https://bugs.kde.org/show_bug.cgi?id=383281 --- Comment #5 from Tanner H --- I had a little spare time this afternoon, so I tried running 3.2 RC with OpenGL logging enabled. The new crash log suggests qopenglfunctions_3_0.h as a possible culprit: krita.exe caused an Access Violation at location 7FF92E1AB76A in module libkritaui.dll Reading from location 0110. AddrPC Params 7FF92E1AB76A 0F3730E0 00B200F2 02EAEE40 libkritaui.dll!renderCanvasGL [C:/dev/i/include/QtGui/qopenglfunctions_3_0.h @ 953] 7FF92E1AB891 005F8BD0 68A160D9 12280F80 libkritaui.dll!paintGL [C:/dev/krita-3.2.0-rc.1/libs/ui/opengl/kis_opengl_canvas2.cpp @ 342] No idea if this helps, but perhaps narrows it to two related commits unique to 3.2: https://github.com/KDE/krita/commit/331b4501488aaa02afbc964272164a34b86f5ef3 https://github.com/KDE/krita/commit/540dc93b4b73c2adde58e0bdf389c5448df7f3ab (Apologies for linking direct to GitHub commit pages; I was using them to search potentially related commits.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383281] Krita on Windows 10: always crashes File > New, File > Open, File > Open Recent
https://bugs.kde.org/show_bug.cgi?id=383281 --- Comment #4 from Tanner H --- Just tried 4.0 pre-alpha (krita-x64-cbd6726-appveyor-0.1.1.216) and yes, it also crashes when OpenGL is enabled. Disabling OpenGL solves the crash. (Also, I doubt it's helpful, but changing the scaling mode and/or texture buffer settings makes no difference.) I am not sure the exact name of the Intel HD chip. The Intel control panel lists it as "Intel HD Graphics (Core i5)". GPU-Z links it to this page: https://www.techpowerup.com/gpudb/2028/hd-graphics In case it's useful, here is the backtrace for the 4.0 pre-alpha crash: Error occurred on Wednesday, August 16, 2017 at 09:04:02. krita.exe caused an Access Violation at location 7FF93F4DD28E in module libkritaui.dll Reading from location 0110. AddrPC Params 7FF93F4DD28E 163A47D0 00B200F2 02B21FF0 libkritaui.dll!KisOpenGLCanvas2::renderCanvasGL 7FF93F4DD421 005F8C30 68A159B9 188429A0 libkritaui.dll!KisOpenGLCanvas2::paintGL 00D37E8D 08B4AB28 7FF93F5A4533 188429A0 Qt5Widgets.dll!QOpenGLWidget::resizeEvent 00D1DB9E 005FFB90 005FFB90 Qt5Widgets.dll!QWidget::event 00CDA33C 155B6E00 17E08D10 005F8B00 Qt5Widgets.dll!QApplicationPrivate::notify_helper 00CDF6A0 163A47D0 Qt5Widgets.dll!QApplication::notify 7FF93F5F77A6 0001 00CDF6A0 155B6E00 libkritaui.dll!KisApplication::notify 68A0E312 0001 0001 Qt5Core.dll!QCoreApplication::notifyInternal2 00D15DD6 61977540 00D126D5 02B51760 Qt5Widgets.dll!QWidgetPrivate::sendPendingMoveAndResizeEvents 00D19E22 17E08D10 0001 Qt5Widgets.dll!QWidgetPrivate::show_helper 00D19D2A 17E08D10 00D11AD3 005F8D20 Qt5Widgets.dll!QWidgetPrivate::showChildren 00D19E3F 0001 0001 17E08D10 Qt5Widgets.dll!QWidgetPrivate::show_helper 00D1D342 162F6020 0001 Qt5Widgets.dll!QWidget::setVisible 00D19D87 162F6020 00D11AD3 005F8EC0 Qt5Widgets.dll!QWidgetPrivate::showChildren 00D19E3F 0001 162F6020 Qt5Widgets.dll!QWidgetPrivate::show_helper 00D1D342 0018 0018 Qt5Widgets.dll!QWidget::setVisible 00D19D87 165ACC00 Qt5Widgets.dll!QWidgetPrivate::showChildren 00D19E3F 0001 165ACC00 Qt5Widgets.dll!QWidgetPrivate::show_helper 00D1D342 0018 0018 Qt5Widgets.dll!QWidget::setVisible 00D19D87 0018 Qt5Widgets.dll!QWidgetPrivate::showChildren 00D19E3F 08CA3680 Qt5Widgets.dll!QWidgetPrivate::show_helper 00D1D342 68B42200 7FF97214AF7E 68B42200 Qt5Widgets.dll!QWidget::setVisible 00E39990 02B21FF0 68A159B9 02B51760 Qt5Widgets.dll!QMdiSubWindow::changeEvent 00D1D65A 18840420 1883FBB0 18840450 Qt5Widgets.dll!QWidget::event 00E3A2B2 005FFB90 005FFB90 Qt5Widgets.dll!QMdiSubWindow::event 00CDA33C 155B6E00 188231C0 005F9880 Qt5Widgets.dll!QApplicationPrivate::notify_helper 00CDF6A0 005F972F 18773460 Qt5Widgets.dll!QApplication::notify 7FF93F5F77A6 157B8700 005F9880 005F97DF libkritaui.dll!KisApplication::notify 68A0E312 68CED240 0004004B Qt5Core.dll!QCoreApplication::notifyInternal2 00D19424 1883FBB0 1883FBB0 1883FBB0 Qt5Widgets.dll!QWidget::setWindowState 00D19BD3 157B8640 00E30C0E 68B42200 Qt5Widgets.dll!QWidget::showMaximized 00E3A07E 155B6E00 6889DE9B 17C864F0 Qt5Widgets.dll!QMdiSubWindow::eventFilter 68A0E0DD 005FFB90 005FFB90 Qt5Core.dll!QCoreApplicationPrivate::sendThroughObjectEventFilters 00CDA315 155B6E00 155B7000 005F9DD0 Qt5Widgets.dll!QApplicationPrivate::notify_helper 00CDF6A0 68A2EC40 165ACC00 Qt5Widgets.dll!QApplication::notify 7FF93F5F77A6 005F9DB0 0104D612 68B42200 libkritaui.dll!KisApplication::notify 68A0E312 18836810 08CA3680 187BA980 Qt5Core.dll!QCoreApplication::notifyInternal2 00D19424 165ACC00 005F9EB0 0
[krita] [Bug 383281] Krita on Windows 10: always crashes File > New, File > Open, File > Open Recent
https://bugs.kde.org/show_bug.cgi?id=383281 --- Comment #3 from Boudewijn Rempt --- Hm... That definitely needs updating, but why it should crash... Could you also check whether the 4.0 pre-alpha crashes before updating the driver? I guess that the display chip is an HD3000? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383281] Krita on Windows 10: always crashes File > New, File > Open, File > Open Recent
https://bugs.kde.org/show_bug.cgi?id=383281 --- Comment #2 from Tanner H --- Hi Boudewijn. Thank you for following-up. On 3.2 RC, if I disable OpenGL, the crash disappears. Just to confirm, I downloaded Krita 3.1.4 portable this morning onto this same PC. Even with OpenGL enabled, there is no crash. File > New and File > Open/Open Recent work flawlessly in 3.1.4, with or without OpenGL enabled. As you can see from my System Info report (below), this PC is 6-7 years old and using its original integrated Intel display chip. Windows lists the driver date as November 2012, and if you want, I can try and find an updated version to download. (I didn't want to touch the driver yet, in case you needed details from this PC "as is"). Here is the full System Info report: OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.15063 Pretty Productname: Windows 10 Product Type: windows Product Version: 10 OpenGL Info Vendor: Intel Renderer: Intel(R) HD Graphics Version: 2.1.0 - Build 8.15.10.2900 Shading language: 1.20 - Intel Build 8.15.10.2900 Version: 2.1 Supports deprecated functions: true -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383281] Krita on Windows 10: always crashes File > New, File > Open, File > Open Recent
https://bugs.kde.org/show_bug.cgi?id=383281 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||[email protected] Severity|normal |crash --- Comment #1 from Boudewijn Rempt --- Weird... Since there's no difference in our opengl code between 3.1 and 3.2... Does this still happen when you disable opengl? Have had any recent updates for your windows display driver? Can you tell us which display chip you have, and the version of the driver? Please go to the help menu, select system information and paste the information from the dialog. -- You are receiving this mail because: You are watching all bug changes.
