https://bugs.kde.org/show_bug.cgi?id=472477

Marco Martin <notm...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |notm...@gmail.com

--- Comment #2 from Marco Martin <notm...@gmail.com> ---
the interesting part of the backtrace is the following. I windoer if is nvidia
related and if could potentially be solved by getting back to the basic render
loop in plasma on nvidia which seems we'll have to

#3  0x00007ff213fc1f5a in
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState
const&, QSGMaterial*, QSGMaterial*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x00007ff213faa80d in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
() from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x00007ff213fafa55 in QSGBatchRenderer::Renderer::renderBatches() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x00007ff213fb05b6 in QSGBatchRenderer::Renderer::render() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007ff213f97f00 in QSGRenderer::renderScene(QSGBindable const&) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007ff213f983b3 in QSGRenderer::renderScene(unsigned int) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007ff213ffb663 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007ff214068139 in QQuickWindowPrivate::renderSceneGraph(QSize const&,
QSize const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007ff214009597 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x00007ff21400a46f in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x00007ff2120cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ff211ea7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#15 0x00007ff211f285bc in ?? () from /lib/x86_64-linux-gnu/libc.so.6

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to