From f077bf13efee6d57261f76544e89a10acafb5a9c Mon Sep 17 00:00:00 2001 From: Lars Knoll Date: Thu, 11 Jun 2015 16:35:11 +0200 Subject: Clean up ExecutionContext's for QML Create a specialized QmlContext instead of re-using a call context with a QQmlContextWrapper as activation object. This saves some memory and opens up the route to getting rid of the context wrapper in a future commit. Change-Id: I1591c73932a08564fddf5137ac05bbc6f31dd4d5 Reviewed-by: Simon Hausmann --- src/qml/jsruntime/qv4debugging.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/qml/jsruntime/qv4debugging.cpp') diff --git a/src/qml/jsruntime/qv4debugging.cpp b/src/qml/jsruntime/qv4debugging.cpp index cd9e1e3936..7bd5d49f3c 100644 --- a/src/qml/jsruntime/qv4debugging.cpp +++ b/src/qml/jsruntime/qv4debugging.cpp @@ -498,7 +498,7 @@ QVector Debugger::getScopeTypes(int frame) Scope scope(m_engine); Scoped sctxt(scope, findContext(m_engine->currentContext(), frame)); - if (!sctxt || sctxt->d()->type < Heap::ExecutionContext::Type_SimpleCallContext) + if (!sctxt || sctxt->d()->type < Heap::ExecutionContext::Type_QmlContext) return types; ScopedContext it(scope, sctxt->d()); -- cgit v1.2.3