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
There is a global thread-safe priority queue for V8Guard instances. There are flaws in the current implementation.
There is no synchronization between take() and add() in the daemon thread.
The daemon thread doesn't check whether a V8Guard instance is closed or not.
That creates a slight chance of adding a closed V8Guard in the daemon thread when there is constant heavy load. That results in executions terminated early.
Impact Versions
v3.1.3-v3.1.6
Solution
Add synchronized check against V8Guard.isClosed().
The text was updated successfully, but these errors were encountered:
Problem
There is a global thread-safe priority queue for
V8Guard
instances. There are flaws in the current implementation.take()
andadd()
in the daemon thread.V8Guard
instance is closed or not.That creates a slight chance of adding a closed
V8Guard
in the daemon thread when there is constant heavy load. That results in executions terminated early.Impact Versions
v3.1.3-v3.1.6
Solution
V8Guard.isClosed()
.The text was updated successfully, but these errors were encountered: