Hello,
I'm using clearscripts V8 facilities to process datasets in an ETL application. For each table I create a V8Runtime, for each row a V8Engine. For testing purposes I hand over no HostObjects right now, the Javascript-Code does nothing, and I don't read something back to the .NET side. After each script processing I dispose the V8Engine and trigger a CollectGarbage on the V8Runtime. After that I output the HeapInfo.
The HeapInfo suggests, that the memory-consumption of the v8 runtime remains more or less constant. But using Sysinternals Process-Explorer reveals, that the process working set as well as private bytes grow constantly to serveral GBs. When I'm short circuiting the part of my code which uses clearscript and therefore don't interact with V8 the memory-consumption of my .NET app is perfectly constant.
Has anyone experienced something similar and give me a hint to common pitfalls?
Thank you and andvance and best regards
Joachim
I'm using clearscripts V8 facilities to process datasets in an ETL application. For each table I create a V8Runtime, for each row a V8Engine. For testing purposes I hand over no HostObjects right now, the Javascript-Code does nothing, and I don't read something back to the .NET side. After each script processing I dispose the V8Engine and trigger a CollectGarbage on the V8Runtime. After that I output the HeapInfo.
The HeapInfo suggests, that the memory-consumption of the v8 runtime remains more or less constant. But using Sysinternals Process-Explorer reveals, that the process working set as well as private bytes grow constantly to serveral GBs. When I'm short circuiting the part of my code which uses clearscript and therefore don't interact with V8 the memory-consumption of my .NET app is perfectly constant.
Has anyone experienced something similar and give me a hint to common pitfalls?
Thank you and andvance and best regards
Joachim