Closed Bug 555299 Opened 15 years ago Closed 7 years ago

Same CallStackNode entry is popped off the ActionScript callstack twice

Categories

(Tamarin Graveyard :: Virtual Machine, defect, P4)

Product:
Tamarin Graveyard
Component:
Virtual Machine
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
Q1 12 - Brannan

People

(Reporter: mike, Unassigned)

Details

As first described in bug 555031: A strange quirk: It turns out that sometimes, the same CallStackNode is essentially popped off the stack twice!!! E.g. if ActionScript code calls a [native] function, then when it is exiting, first MethodInfo::debugEnterExitWrapper32() calls MethodEnv::debugExit(), which pops the stack with "core->callStack = callstack->next", and then, MethodInfo::debugEnterExitWrapper32() implicitly invokes ~CallStackNode, which does the same thing again! Luckily, the way it is done does not corrupt the stack. We should clean this up, but since it is harmless, I don't want to take that risk in flash10.1.
Flags: flashplayer-qrb+
Priority: -- → P4
Target Milestone: --- → flash10.2
Summary: Same entry is popped off the ActionScript callstack twice → Same CallStackNode entry is popped off the ActionScript callstack twice
Severity: normal → minor
Flags: flashplayer-injection-
Flags: flashplayer-bug-
Target Milestone: Q3 11 - Serrano → Q1 12 - Brannan
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.