| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
|
||
| if (per_process::v8_initialized) { | ||
| performance_state_->Mark(performance::NODE_PERFORMANCE_MILESTONE_V8_START, | ||
| performance::performance_v8_start); |
There was a problem hiding this comment.
| performance::performance_v8_start); | |
| performance::performance_v8_start); |
nit: we can align these vertically
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #40405 Refs: electron/electron#31349 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
PR-URL: #40405 Refs: electron/electron#31349 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
| Back | FazBrowse Home | New Git URL |
Refs:
When Node.js is started within Electron's environment it doesn't initialize V8, so V8's start time is never set. As a result, Electron logs V8's start time as 0 and it breaks timestamps in the trace log.
This change fixes the issue by adding logic to log V8's start time only when V8 is initialized by Node.js.