diff options
| author | Aaron Kennedy <aaron.kennedy@nokia.com> | 2009-11-09 01:33:14 (GMT) |
|---|---|---|
| committer | David Boddie <dboddie@trolltech.com> | 2009-11-11 16:06:45 (GMT) |
| commit | d4e310005a2fbd34b36c46431bc4ad6c18011466 (patch) | |
| tree | 6d4f9451f259ef00f1eb9b342ff7b9176b594751 /src/dbus/qdbusconnection_p.h | |
| parent | 0a4adee8f1947beaac38a21b1eb8b031b4cdbc52 (diff) | |
| download | Qt-d4e310005a2fbd34b36c46431bc4ad6c18011466.zip Qt-d4e310005a2fbd34b36c46431bc4ad6c18011466.tar.gz Qt-d4e310005a2fbd34b36c46431bc4ad6c18011466.tar.bz2 | |
During a GC mark the scope chain of QScriptContexts
It appears that simply being in the scope chain of an existant frame
isn't sufficient to be marked. This can lead to a QScriptContext
scope chain that contains a JSObject that has been collected.
For example, this code:
QScriptContext *ctxt = engine->pushContext();
ctxt.pushScope(engine->newObject());
previouslyCreatedFunctionObject.call(); // causes a GC
can lead to the object added to the scope chain to have become
invalid. This leads to hilarity later on.
Reviewed-by: Kent Hansen
Diffstat (limited to 'src/dbus/qdbusconnection_p.h')
0 files changed, 0 insertions, 0 deletions