This would appear to be a (now resolved) Qt bug, specifically QTBUG-48391[1]. The backtrace here (35 frames of Qt on top of Twinkle's run() method) looks eerily identical to the one in QTBUG-48391 (save for two extra frames at the top in our case). For the record, the fix[2] seems to have made it in Qt 5.9.
This would appear to be a (now resolved) Qt bug, specifically QTBUG-48391[1]. The backtrace here (35 frames of Qt on top of Twinkle's run() method) looks eerily identical to the one in QTBUG-48391 (save for two extra frames at the top in our case). For the record, the fix[2] seems to have made it in Qt 5.9.
[1] https:/ /bugreports. qt.io/browse/ QTBUG-48391 /codereview. qt-project. org/c/qt/ qtbase/ +/188320
[2] https:/