SCI: Avoid incrementing lockers of deleted script
Having a deleted script with non-zero lockers had the side effect of
making the deleted script re-appear in the GC's work list, including
any (deleted) objects in the script.
This should be the root cause of bugs #3299458 and #3295849, so
also delete the workaround added for that in 35086fe1
.
This commit is contained in:
parent
3ed095434f
commit
c01fed7159
3 changed files with 4 additions and 9 deletions
|
@ -259,7 +259,7 @@ reg_t kDisposeScript(EngineState *s, int argc, reg_t *argv) {
|
|||
|
||||
SegmentId id = s->_segMan->getScriptSegment(script);
|
||||
Script *scr = s->_segMan->getScriptIfLoaded(id);
|
||||
if (scr) {
|
||||
if (scr && !scr->isMarkedAsDeleted()) {
|
||||
if (s->_executionStack.back().addr.pc.segment != id)
|
||||
scr->setLockers(1);
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue