From 8139d43c294ef68460c6749a0d1aa5ad0ba37910 Mon Sep 17 00:00:00 2001 From: Kai Koehne Date: Wed, 10 Apr 2013 15:03:02 +0200 Subject: [PATCH] Fix qml engine lockup when debugging an app run in terminal The default timeout for the timer is set to 0 for projects that have the 'run in terminal' option checked in the run settings. Make sure that this timeout is set to a reasonable number once the first connect fails, before we retry. Task-number: QTCREATORBUG-8931 Change-Id: Iaa8acb50d76f182ceda77f8e6923738ad79ff445 Reviewed-by: Friedemann Kleint Reviewed-by: Aurindam Jana --- src/plugins/debugger/qml/qmlengine.cpp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/plugins/debugger/qml/qmlengine.cpp b/src/plugins/debugger/qml/qmlengine.cpp index 1c5690c700a..822a835a367 100644 --- a/src/plugins/debugger/qml/qmlengine.cpp +++ b/src/plugins/debugger/qml/qmlengine.cpp @@ -401,8 +401,10 @@ void QmlEngine::tryToConnect(quint16 port) if (state() == EngineRunRequested) { if (isSlaveEngine()) { // Probably cpp is being debugged and hence we did not get the output yet. - if (!masterEngine()->isDying()) + if (!masterEngine()->isDying()) { + m_noDebugOutputTimer.setInterval(4000); m_noDebugOutputTimer.start(); + } else appStartupFailed(tr("No application output received in time")); } else {