Perturbing the test case, I crash with a zero callee token @..ab. It's the same problem: the callee token is busted.
Bug 1666140 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Perturbing the test case, I crash with a zero callee token @..ab. It's the same problem: the callee token is busted. It's possible we've not run into this before because there is an allocation failure here, and that we've not tested that.
Perturbing the test case, I crash with a zero callee token @..ab. It's the same problem: the callee token is busted. It's possible we've not run into this before because there is an allocation failure here, and that we've not tested that. We are on the return path from the call into wasm and we're trying to box up a bigint, but can't.
Perturbing the test case, I crash with a zero callee token @..ab. It's the same problem: the callee token is busted. It's possible we've not run into this before because there is an allocation failure here, and that we've not tested that. We are on the return path from the call into wasm and we're trying to box up a bigint, but can't. Looking at the code, it does not seem like it has a coherent view of what the stack looks like. The jump from within the bigint boxing out to the throw code looks particularly wrong.