Memory leak?

[roberttekaat-ireckonu]

In my solution I create and dispose a lot of V8ScriptEngine instances. However, now that load on my application is increasing, it turns out not all memory is released. I tried to get a grip on what is happening by comparing snapshots, but I dont see much there, so cannot help you with that.

[ClearScriptLib]

Hi @roberttekaat-ireckonu,

Unfortunately, we can't investigate this issue without a test case. If you can reproduce it via a small test program, we'll be happy to take a look.

Also, V8 is native code, so if you're examining memory snapshots, be sure to include native (unmanaged) memory.

Thanks!

[simontom]

We use a similar approach and have the same(?) problem.
There might be a problem with a leak somewhere in our codebase, but one thing we came across is tracking added host objects in the "ConditionalWeakTable" - that's what AI said, to be honest 😀. Is there any recommendation to what/how to use that? We add like tens of host objects using AddHostObject (and its close friend AddHostObject to global), some of them outlive the lifecycle of the Engine (some are the Scoped, some Transient-like, and the rest are Singletons).
AI said that might be some of the leaks because the table doesn't release its nodes and only Transient approach should be used instead. (Even tho' the value gets disposed, the key keeps the node stale in the table.)

So, might that be a true?
Are there any limitations / best practices how to add the host objects correctly?
Can there by such a problem (or any) even tho' we dispose the engine every time after the run finishes?