[wasm] Fix Wasm interpreter DCHECK
Remove DCHECK because the interpreter may still have activations when the isolate is torn down. This can happen in particular, when {quit} is called in d8. A test for this will follow when v8:9209 is resolved. Change-Id: Ia3ab0daa061d6427df3f778ba5fb195218910280 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1594560 Commit-Queue: Frederik Gossen <frgossen@google.com> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#61232}
This commit is contained in:
parent
b41c32421e
commit
5c182baa14
@ -146,8 +146,6 @@ class InterpreterHandle {
|
||||
interpreter_(isolate, module_, GetBytes(*debug_info),
|
||||
handle(debug_info->wasm_instance(), isolate)) {}
|
||||
|
||||
~InterpreterHandle() { DCHECK_EQ(0, activations_.size()); }
|
||||
|
||||
WasmInterpreter* interpreter() { return &interpreter_; }
|
||||
const WasmModule* module() const { return module_; }
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user