-
-
Notifications
You must be signed in to change notification settings - Fork 35.6k
v8: consider cherry-picking 3d750c2 to v24.x #58744
Copy link
Copy link
Closed
Labels
v24.xIssues that can be reproduced on v24.x or PRs targeting the v24.x-staging branch.Issues that can be reproduced on v24.x or PRs targeting the v24.x-staging branch.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.
Metadata
Metadata
Assignees
Labels
v24.xIssues that can be reproduced on v24.x or PRs targeting the v24.x-staging branch.Issues that can be reproduced on v24.x or PRs targeting the v24.x-staging branch.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.
Type
Fields
Give feedbackNo fields configured for issues without a type.
13.7.92 contains an explicit resource management fix, v8/v8@3d750c2.
Currently, the feature is broken entirely if the
[await] usingvariable gets bound to a closure, with the disposer never being invoked.When running the above example in v24.x, after the closure is created, V8 does not invoke the disposer on exiting the block.
cc: @targos