Attachment 139302 Details for Bug 106372 – gdb backtrace of hanging plasmashell thread

gdb backtrace of hanging plasmashell thread

backtrace_plasmashell.txt (text/plain), 3.48 KB, created by Tobias Klausmann on 2018-05-03 12:02:53 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Tobias Klausmann

Created: 2018-05-03 12:02:53 UTC

Size: 3.48 KB

patch

obsolete

>Thread 1 (Thread 0x7ffff7f9c5c0 (LWP 2265)):
>#0  0x00007ffff1302179 in poll () at /lib64/libc.so.6
>#1  0x00007ffff635a387 in _xcb_conn_wait () at /usr/lib64/libxcb.so.1
>#2  0x00007ffff635c09a in xcb_wait_for_special_event () at /usr/lib64/libxcb.so.1
>#3  0x00007fffd139240b in dri3_wait_for_event_locked () at /usr/lib64/libGLX_mesa.so.0
>#4  0x00007fffd1392568 in dri3_find_back () at /usr/lib64/libGLX_mesa.so.0
>#5  0x00007fffd139364e in dri3_get_buffer.isra () at /usr/lib64/libGLX_mesa.so.0
>#6  0x00007fffd139441f in loader_dri3_get_buffers () at /usr/lib64/libGLX_mesa.so.0
>#7  0x00007fff476713cf in intel_update_renderbuffers () at /usr/lib64/dri/i965_dri.so
>#8  0x00007fff476716d1 in intel_prepare_render () at /usr/lib64/dri/i965_dri.so
>#9  0x00007fff4766cbbc in brw_clear () at /usr/lib64/dri/i965_dri.so
>#10 0x00007ffff577e467 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib64/libQt5Quick.so.5
>#11 0x00007ffff5783acc in QSGBatchRenderer::Renderer::render() () at /usr/lib64/libQt5Quick.so.5
>---Type <return> to continue, or q <return> to quit---
>#12 0x00007ffff577493d in QSGRenderer::renderScene(QSGBindable const&) () at /usr/lib64/libQt5Quick.so.5
>#13 0x00007ffff5774dcb in QSGRenderer::renderScene(unsigned int) () at /usr/lib64/libQt5Quick.so.5
>#14 0x00007ffff57ac940 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () at /usr/lib64/libQt5Quick.so.5
>#15 0x00007ffff580afe8 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib64/libQt5Quick.so.5
>#16 0x00007ffff579f784 in  () at /usr/lib64/libQt5Quick.so.5
>#17 0x00007ffff5815b1e in QQuickWindow::event(QEvent*) () at /usr/lib64/libQt5Quick.so.5
>#18 0x0000555555583a4b in  ()
>#19 0x00007ffff2dc601c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
>#20 0x00007ffff2dcd314 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
>#21 0x00007ffff1be9148 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
>#22 0x00007ffff21754c1 in QWindowPrivate::deliverUpdateRequest() () at /usr/lib64/libQt5Gui.so.5
>#23 0x00007ffff2175989 in QWindow::event(QEvent*) () at /usr/lib64/libQt5Gui.so.5
>#24 0x00007ffff5815ad5 in QQuickWindow::event(QEvent*) () at /usr/lib64/libQt5Quick.so.5
>#25 0x0000555555583a4b in  ()
>#26 0x00007ffff2dc601c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
>#27 0x00007ffff2dcd314 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
>#28 0x00007ffff1be9148 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
>#29 0x00007ffff1c3ffbe in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
>#30 0x00007ffff1c40709 in  () at /usr/lib64/libQt5Core.so.5
>#31 0x00007fffeb919277 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
>#32 0x00007fffeb9194b0 in  () at /usr/lib64/libglib-2.0.so.0
>#33 0x00007fffeb91953c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
>#34 0x00007ffff1c40a0f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
>    at /usr/lib64/libQt5Core.so.5
>#35 0x00007fffe3f4e781 in  () at /usr/lib64/libQt5XcbQpa.so.5
>#36 0x00007ffff1be795a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
>#37 0x00007ffff1bf0494 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
>#38 0x0000555555574e23 in  ()
>#39 0x00007ffff1234a87 in __libc_start_main () at /lib64/libc.so.6
>#40 0x00005555555751ca in _start ()

Actions: View

Attachments on bug 106372: 139302 | 139311

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.