Skip to content

worker: reset `Isolate` stack limit after entering `Locker`

It turns out that using v8::Locker undoes the effects of passing an explicit stack limit as part of the Isolate’s resource constraints.

Therefore, reset the stack limit manually after entering a Locker.

Refs: https://github.com/nodejs/node/pull/26049#issuecomment-580668530

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

Merge request reports

Loading