{"push_id":2417702776,"size":1,"distinct_size":1,"ref":"refs/heads/backport-v8-fix","head":"f2a75d1261adf315fc84273ea2f6efad84d19ad3","before":"17f186bc12a6b90bafede22d8388f30c11103594","commits":[{"sha":"f2a75d1261adf315fc84273ea2f6efad84d19ad3","author":{"name":"Myles Borins","email":"cd43a902f810aceb1f48509b3e1828103b19f99a@google.com"},"message":"deps: V8: backport 596d55a from upstream\n\nDid not remove ActivationsFinder from `src/runtime/runtime-compiler.cc`\nas in the original commit as the Class is still being used prior to\nf0acede landing\n\nOriginal Commit Message:\n\n    Deoptimization and multithreading.\n\n    When using Lockers and Unlockers it is possible to create a\n    scenario where multiple threads point to the same optimized\n    code object. When that happens, if one of the threads triggers\n    deoptimization, then the stack replacement needs to happen in\n    the stacks of all threads.\n    With this CL, the deoptimizer visits all threads to do so.\n    The CL also adds three tests where V8 used to crash due to this\n    issue.\n\n    Bug: v8:6563\n    Change-Id: I74e9af472d4833aa8d13e579df45133791f6a503\n    Reviewed-on: https://chromium-review.googlesource.com/670783\n    Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>\n    Commit-Queue: Juliana Patricia Vicente Franco <jupvfranco@google.com>\n    Cr-Commit-Position: refs/heads/master@{#48060}\n\nRefs: https://github.com/v8/v8/commit/596d55a\nRefs: https://github.com/v8/v8/commit/f0acede\nFixes: https://github.com/nodejs/node/issues/19274","distinct":true,"url":"https://api.github.com/repos/MylesBorins/node/commits/f2a75d1261adf315fc84273ea2f6efad84d19ad3"}]}
{"actor":{"display_login":"MylesBorins"}}