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/qv4functionobject.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/qml/jsruntime/qv4functionobject.cpp') diff --git a/src/qml/jsruntime/qv4functionobject.cpp b/src/qml/jsruntime/qv4functionobject.cpp index 622610ade3..d8cdda477a 100644 --- a/src/qml/jsruntime/qv4functionobject.cpp +++ b/src/qml/jsruntime/qv4functionobject.cpp @@ -457,7 +457,7 @@ ReturnedValue ScriptFunction::call(const Managed *that, CallData *callData) ScopedValue result(scope, Q_V4_PROFILE(v4, f->function())); if (f->function()->compiledFunction->hasQmlDependencies()) - QmlContextWrapper::registerQmlDependencies(ctx->d()->engine, f->function()->compiledFunction); + QmlContextWrapper::registerQmlDependencies(scope.engine, f->function()->compiledFunction); return result->asReturnedValue(); } -- cgit v1.2.1