You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been noticing that sometimes CPU would get stuck to 100% (per core) since the upgrade to 5.5. After some investigation I've concluded that this is the likely culprit. Now I've been running the patched version of V8 since a couple of days and it looks like the issue is resolved.
This is what I did:
cherry-picked commit ac0fe8ec from V8 upstream (v8/v8@ac0fe8e)
@andrea-s Thank you very much for that information!
We're close to releasing Version 5.5.1 paired with V8 6.3. It looks like the V8 fix you linked will not be merged into the 6.3 stable branch, so we'll modify V8Update to apply it explicitly.
Hey,
just wanted to let you know that there is a deadlock issue that affects V8 (and ClearScript) - as detailed here: https://bugs.chromium.org/p/v8/issues/detail?id=6933
I've been noticing that sometimes CPU would get stuck to 100% (per core) since the upgrade to 5.5. After some investigation I've concluded that this is the likely culprit. Now I've been running the patched version of V8 since a couple of days and it looks like the issue is resolved.
This is what I did:
Basically the same thing node did here: nodejs/node#17695
I'm attaching the corresponding patch here - has anyone noticed the same behavior with ClearScript 5.5?
0001-interpreter-Remove-TryInstallOptimizedCode.patch,txt
The text was updated successfully, but these errors were encountered: