There appears to be a memory‑related regression when SSR.Net is used together with ClearScript 7.5.1. After upgrading ClearScript, applications using JavaScriptEnginePool show steadily increasing memory usage, especially under load. The issue seems related to changes in ClearScript 7.5.1 around explicit resource management and disposal of V8 objects.
Because SSR.Net reuses V8 engines through pooling, it may not be fully compatible with the changes introduced in ClearScript 7.5.1.
We unfortunately didn’t notice this before deploying to production, but we were able to reproduce it with a k6 load test in other environments as well.
More info here perhaps:
ClearFoundry/ClearScript#708
V8 should still be the fastest alternative, so I’m guessing it’s the most commonly used engine with this library. Have you noticed any issues?
There appears to be a memory‑related regression when SSR.Net is used together with ClearScript 7.5.1. After upgrading ClearScript, applications using JavaScriptEnginePool show steadily increasing memory usage, especially under load. The issue seems related to changes in ClearScript 7.5.1 around explicit resource management and disposal of V8 objects.
Because SSR.Net reuses V8 engines through pooling, it may not be fully compatible with the changes introduced in ClearScript 7.5.1.
We unfortunately didn’t notice this before deploying to production, but we were able to reproduce it with a k6 load test in other environments as well.
More info here perhaps:
ClearFoundry/ClearScript#708
V8 should still be the fastest alternative, so I’m guessing it’s the most commonly used engine with this library. Have you noticed any issues?