diff options
| author | Simon Hausmann <[email protected]> | 2014-01-16 13:08:37 +0100 |
|---|---|---|
| committer | The Qt Project <[email protected]> | 2014-01-16 19:20:03 +0100 |
| commit | 5d15f9704783e5eafc9ba77740aae85aeac01d24 (patch) | |
| tree | 9dc30ad9c586ea16efba81c78da58df109cfa931 /src/qml/jsruntime/qv4functionobject.cpp | |
| parent | 73f4fdbef816ff623142bee6c235f06c4bdf58d3 (diff) | |
Fix failing context->next != 0x1 assertion
After commit bf173fe5da381c88343296ca33ef6b06389c6d20 context objects are
always on the GC heap and no more in that special linked list or stack
allocated, so the next pointer became dangling/uninitialized and asserting on
it was bound to fail randomly.
Since we no more allocate contexts on the stack, we can safely remove the
assertion.
Task-number: QTBUG-35917
Change-Id: I104bd129c6c32f46a6302052f563abdf926cb879
Reviewed-by: Albert Astals Cid <[email protected]>
Reviewed-by: Jan Arve Sæther <[email protected]>
Diffstat (limited to 'src/qml/jsruntime/qv4functionobject.cpp')
| -rw-r--r-- | src/qml/jsruntime/qv4functionobject.cpp | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/qml/jsruntime/qv4functionobject.cpp b/src/qml/jsruntime/qv4functionobject.cpp index 6e5c137e0b..ce81282aa3 100644 --- a/src/qml/jsruntime/qv4functionobject.cpp +++ b/src/qml/jsruntime/qv4functionobject.cpp @@ -133,9 +133,6 @@ void FunctionObject::init(const StringRef n, bool createProto) type = Type_FunctionObject; needsActivation = true; strictMode = false; -#ifndef QT_NO_DEBUG - assert(scope->next != (ExecutionContext *)0x1); -#endif if (createProto) { Scoped<Object> proto(s, scope->engine->newObject(scope->engine->protoClass)); |