Hi,
This is a relate the following question.
https://developer.milestonesys.com/s/question/0D50O00004STMALSA5/repeat-switching-the-view-with-rgbvideoenhancement-plugin
Under Smart Client 2018R2 we confirmed it improved but we see floating window are increate the memory.
Could you confirm it ?
For example;
-
Create the view (1x1) with RGBVideoEnhancement plugin.
-
Click “Send view to Floating Window” and wait a few seconds.
-
Close the floating window.
-
Repeat 2) and 3).
then
PrivateBytes, VirtualBytes and .net resources(Bytes in all heaps / GC Handles) are increasing.
Our test condition:
Recording sever:XProtect 2018 R1 Corporate
Smart Client:2018 R2
MIP SDK : 2018 R1 *We used the sample of 2018 R1
When working with the bug found in Smart Client 2018R1 Milestone Development was also made aware that the RGBVideoEnhancement plugin sample is not correct:
--
There is a finalizer destructor missing in the sample the RGBHandling.cpp file. This is nessesary when called from c# to handle clean up from the garbage collector.
public: !Transform()
{
}
When we added this it worked fine and all memory was relased.
--
Please use the sample from MIP SDK 2018R2 (or alternatively correct the sample in MIP SDK 2018R1 according to these instructions).
Thank you for your advice.
We updated to MIP SDK 2018 R2 and confirmed again the RGBVideoEnhancement.
It looks increase the memory for us(Please see the attached file).
Is there any problem of our condition?
Recording sever:XProtect 2018 R2 Essential+
Smart Client:2018 R2
MIP SDK : 2018 R2
PC
OS:Windows 10 EN
GPU:Nvidia geforce 1060
I cannot reproduce.
Not having a tool for automating the opening of floating windows I have only opened and closed 20 floating windows or so, but doing this I get no indication of a leak.
How many times and how frequent do you open a floating window in your testing?
If you have developed a test tool for automating opening the floating windows can you share it with me?
Thank you for trying to reproduce it.
We repeated about 3000 times using a mouse automation tool.
Can I submit to “My Case” about this because we want to share the tool ?
And if you have some information about leak with Nvidia decording, please let you know.
We are able to reproduce this, our internal bug number is 177457.
Thank you for confirming.
Please let you know if you have the plan to fix .
Smart Client 2018R3 will include a fix. Smart Client 2018R3 is expected to release in October or November.
Thank you for your prompt response. We understand.
