Avoid creating a separate Scope in the ExecutionContextSaver

There's no reason this class should create a scope on it's own.

Change-Id: I93bddea8be42a908a1aca1bcb0ec867aae0d29f8
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/qml/jsruntime/qv4context.cpp b/src/qml/jsruntime/qv4context.cpp
index da76da839b..4053eb4f09 100644
--- a/src/qml/jsruntime/qv4context.cpp
+++ b/src/qml/jsruntime/qv4context.cpp
@@ -234,7 +234,7 @@ bool ExecutionContext::deleteProperty(String *name)
 // Do a standard call with this execution context as the outer scope
 ReturnedValue ExecutionContext::call(Scope &scope, CallData *callData, Function *function, const FunctionObject *f)
 {
-    ExecutionContextSaver ctxSaver(scope);
+    ExecutionContextSaver ctxSaver(scope.engine);
 
     Scoped<CallContext> ctx(scope, newCallContext(function, callData));
     if (f)
@@ -254,7 +254,7 @@ ReturnedValue QV4::ExecutionContext::simpleCall(Scope &scope, CallData *callData
 {
     Q_ASSERT(function->canUseSimpleFunction());
 
-    ExecutionContextSaver ctxSaver(scope);
+    ExecutionContextSaver ctxSaver(scope.engine);
 
     CallContext::Data *ctx = scope.engine->memoryManager->allocSimpleCallContext();