-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix exception ref-count leak in non-ref catch handlers. #12860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4474,6 +4474,10 @@ fn create_catch_block( | |
| } | ||
| if is_ref { | ||
| params.push(exn_ref); | ||
| } else { | ||
| // For non-ref catches, the exnref is consumed here and not | ||
| // passed to the branch target. | ||
| environ.translate_drop_exnref(builder, exn_ref)?; | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't quite understand. The GC ref should logically be held alive by the Wasm stack (in the over-approx table) and then get dropped upon the next GC. Why wasn't that happening? Are we missing a call to If so, then we should do that instead.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We do call |
||
| } | ||
|
|
||
| // Generate the branch itself. | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple things:
GcCompiler::alloc_exn.