croick added a comment.
In D18245#418656 <https://phabricator.kde.org/D18245#418656>, @thiago wrote: > This last backtrace does not show anything stuck. Thread 1 was actively running, in fact (it's inside of malloc). > > Also note your testcase has no window, since the widget is destroyed before app.exec(). But it actually is stuck. That's the backtrace after CTRL+C in gdb of the stuck example and sending SIGSTOP to KDevelop. REPOSITORY R871 DrKonqi REVISION DETAIL https://phabricator.kde.org/D18245 To: croick, sitter, #kdevelop Cc: dfaure, thiago, ossi, plasma-devel, jraleigh, GB_2, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
