Open Bug 1959032 Opened 12 days ago Updated 4 days ago

Rework life cycle of JS::Dispatchable

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

People

(Reporter: yulia, Assigned: yulia)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

As part of atomics.waitAsync, we had extensive discussions regarding the life cycle of JS::Dispatchable. The current lifecycle relies on JS::Dispatchables deleting themselves [1]][2]. waitAsync added an additional deletion related to clearing undispatched classes.

A better pattern here would be to use uniqueptrs or a similar mechanism, and to make clear the ownership relationship between JS::Dispatchables, the embedding, and the engine. A high level description of the plan can be found here.

Blocks: sm-api
You need to log in before you can comment on or make changes to this bug.