067ba2a0c6
Benchmarks or worker threads might never return to the event queue, hence they will never execute the scheduled foreground task to log compiled and published wasm code. This CL adds a stack guard to log the code, to ensure that we also log it for wasm code that never returns to the event queue. R=mstarzinger@chromium.org Bug: v8:9104 Change-Id: I176959cadb4ab3a60153d0717530c032272ad3e8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1561073 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#60879} |
||
---|---|---|
.. | ||
console | ||
cpu-profiler | ||
debugger | ||
heap-profiler | ||
runtime | ||
sessions | ||
type-profiler | ||
BUILD.gn | ||
DEPS | ||
inspector-test.cc | ||
inspector.status | ||
isolate-data.cc | ||
isolate-data.h | ||
json-parse-expected.txt | ||
json-parse.js | ||
OWNERS | ||
protocol-test.js | ||
task-runner.cc | ||
task-runner.h | ||
testcfg.py |