-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
src: ensure V8 initialized before marking milestone #40405
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5 tasks
nodejs-github-bot
added
c++
Issues and PRs that require attention from people who are familiar with C++.
needs-ci
PRs that need a full CI run.
labels
Oct 11, 2021
addaleax
approved these changes
Oct 11, 2021
cjihrig
approved these changes
Oct 11, 2021
joyeecheung
approved these changes
Oct 12, 2021
Mesteery
added
request-ci
Add this label to start a Jenkins CI on a PR.
and removed
needs-ci
PRs that need a full CI run.
labels
Oct 12, 2021
github-actions
bot
removed
the
request-ci
Add this label to start a Jenkins CI on a PR.
label
Oct 12, 2021
Mesteery
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Oct 13, 2021
22 tasks
RaisinTen
reviewed
Oct 14, 2021
|
||
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
performance::performance_v8_start); | |
performance::performance_v8_start); |
nit: we can align these vertically
23 tasks
Landed in ad4e70c |
codebytere
added a commit
that referenced
this pull request
Oct 15, 2021
PR-URL: #40405 Refs: electron/electron#31349 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
This was referenced Oct 16, 2021
2 tasks
25 tasks
targos
pushed a commit
that referenced
this pull request
Nov 4, 2021
PR-URL: #40405 Refs: electron/electron#31349 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Joyee Cheung <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
c++
Issues and PRs that require attention from people who are familiar with C++.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.