Skip to content
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

[v8.x backport] deps: cherry-pick 596d55a from upstream V8 #19486

Conversation

benjamn
Copy link
Contributor

@benjamn benjamn commented Mar 20, 2018

Analogous to this v9.x-staging PR submitted by @MylesBorins: #19477

I can confirm this fixes #19274 for the reproductions I've been using.

Original commit message:

Deoptimization and multithreading.

When using Lockers and Unlockers it is possible to create a
scenario where multiple threads point to the same optimized
code object. When that happens, if one of the threads triggers
deoptimization, then the stack replacement needs to happen in
the stacks of all threads.
With this CL, the deoptimizer visits all threads to do so.
The CL also adds three tests where V8 used to crash due to this
issue.

Bug: v8:6563
Change-Id: I74e9af472d4833aa8d13e579df45133791f6a503
Reviewed-on: https://chromium-review.googlesource.com/670783
Reviewed-by: Jaroslav Sevcik <[email protected]>
Commit-Queue: Juliana Patricia Vicente Franco <[email protected]>
Cr-Commit-Position: refs/heads/master@{#48060}

Refs: v8/v8@596d55a

Analogous to this v9.x-staging PR submitted by @MylesBorins:
nodejs#19477

I can confirm this fixes nodejs#19274 for
the reproductions I've been using.

Original commit message:

    Deoptimization and multithreading.

    When using Lockers and Unlockers it is possible to create a
    scenario where multiple threads point to the same optimized
    code object. When that happens, if one of the threads triggers
    deoptimization, then the stack replacement needs to happen in
    the stacks of all threads.
    With this CL, the deoptimizer visits all threads to do so.
    The CL also adds three tests where V8 used to crash due to this
    issue.

    Bug: v8:6563
    Change-Id: I74e9af472d4833aa8d13e579df45133791f6a503
    Reviewed-on: https://chromium-review.googlesource.com/670783
    Reviewed-by: Jaroslav Sevcik <[email protected]>
    Commit-Queue: Juliana Patricia Vicente Franco <[email protected]>
    Cr-Commit-Position: refs/heads/master@{nodejs#48060}

Refs: v8/v8@596d55a
@nodejs-github-bot nodejs-github-bot added v8 engine Issues and PRs related to the V8 dependency. v8.x labels Mar 20, 2018
@MylesBorins
Copy link
Contributor

@benjamn the v9.x commit will land cleanly on v8.x. Closing this as a dupe so we don't need to get it through review twice. Thanks for opening and testing!

@MylesBorins MylesBorins added the duplicate Issues and PRs that are duplicates of other issues or PRs. label Mar 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs. v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants