Closed Bug 774294 Opened 12 years ago Closed 6 years ago

worker terminate() always fires assertion: "((from == Isolate::RUNNING || from == Isolate::STARTING || from == Isolate::FINISHING || from == Isolate::NEW))" ("../core/Isolate.cpp":380)

Categories

(Tamarin Graveyard :: Workers, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: dschaffe, Unassigned)

References

Details

Attachments

(1 file)

Calling worker.terminiate() in the debug shell always fires the assertion:
"((from == Isolate::RUNNING || from == Isolate::STARTING || from == Isolate::FINISHING || from == Isolate::NEW))" ("../core/Isolate.cpp":380)

Investigating the Isolate.cpp/Aggregate::stateTransition call the function is called twice after terminate():
FINISHING -> TERMINATED  (4->5)
TERMINATED -> TERMINATED (5->5)

the 2nd case is causing the assertion to fail.  Should we allow TERMINATED -> TERMINATED or is the bug in the stateTransition (5,5) call?
Blocks: 695061
Attached file testcase
changeset: 7518:f0a40cb50302
user:      Dan Schaffer <Dan.Schaffer@adobe.com>
summary:   bug 774294: ByteArray uncompress is causing leak failure in debug shells, mark test skip (r=dschaffe)

http://hg.mozilla.org/tamarin-redux/rev/f0a40cb50302
Tamarin is a dead project now. Mass WONTFIX.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Tamarin isn't maintained anymore. WONTFIX remaining bugs.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: