https://bugs.kde.org/show_bug.cgi?id=403086
Bug ID: 403086
Summary: OpenGL Function call without setting up proper context
results in crash on (some?) AMD drivers
Product: krita
Version: 4.1.7
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: crash
Priority: NOR
Component: OpenGL Canvas
Assignee: krita-bugs-n...@kde.org
Reporter: genosim...@gmail.com
Target Milestone: ---
Created attachment 117392
--> https://bugs.kde.org/attachment.cgi?id=117392&action=edit
crashlog.txt
This is a translation of a bug reported on krita's vk.com page
(https://vk.com/topic-38024296_28204669?offset=1120)
A user reports that krita crashes on his system immediately after he tries to
open the popup palette with mouse right click. The log of the crash is attached
to this report.
Cursory lookup suggests that the only possible culprit is the function call
k_glGetSynciv(...) file kis_opengl_canvas2_p.h line 109. Exploring context of
this call, we also quickly arrive at kis_canvas2.cpp, where a warning comment
is placed
void KisCanvas2::slotDoCanvasUpdate()
{
/**
* WARNING: in isBusy() we access openGL functions without making the
painting
* context current. We hope that currently active context will be Qt's one,
* which is shared with our own.
*/
if (m_d->canvasWidget->isBusy()) {
// just restarting the timer
updateCanvasWidgetImpl(m_d->savedUpdateRect);
return;
}
...
Apparently, AMD drivers don't understand the virtues of hope.
--
You are receiving this mail because:
You are watching all bug changes.
