| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
#43781 didn't land on v14.x and v16.x, so this fix doesn't need to land on v14.x and v16.x too. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
Fixed the test failure with tools/run-worker.js. |
Sorry, something went wrong.
|
@legendecas this didn't land cleanly on v18.x - do you mind opening a backport PR? Thank you |
Sorry, something went wrong.
|
#43781 didn't land on v18.x. I'm tagging this as https://github.com/nodejs/node/labels/dont-land-on-v18.x. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Although the performance.timeOrigin is a Web API, Node.js specific extension performance.nodeTiming exposes the process performance milestones in the main thread and the worker threads. In order to avoid exposing negative values in performance.nodeTiming, set the performance.timeOrigin to the start time of the process both in the main thread and worker threads.
Refs: #43781
Fixes #45958, with regression test cases.