When I run PlaybackUser example in ComponentSamples with the live mode, it increase memory consumption until the program memory exhausted.
It seems doing the garbage collection sometimes but increasing memory consumption is faster than decreasing by releasing memory.
Is this normal? And is there any way to prevent the memory exhaustion?
The sample or MIPSDK should not leak memory.
Can you explain a bit more on:
-
What version of MIPSDK ae you using
-
Do you just leave it displaying or do you click/change anything
-
For how long do you need to run before seeing the leak
-
Are you running the sample, or has it been modified
Thanks.
I`m using 2017 R3 version, the exact version should be 11.3a.
I could see the symptom after compiling the sample, let it run and leave it run for around 20 minutes.
I tested it in both ways, just let it run the sample as it is and make it run with in my application.
In case I put the source code in my application consumes the memory faster than the sample but increasing memory is occurred in both cases.
After I run the sample code, what I operate was only changing the mode from playback to live and it only occurs in the live mode.
@Anders B. Christensen
Do you have any opinion for this?
I`m curious that I`m the only person who are experiencing this problem.
There is nothing to do that I can do to fix this.
Somebody advised me to install hotfix, but it didn’t show me any effect.
I update what is happening on another post please refer the post below give me any kind of hint to solve this problem.
https://developer.milestonesys.com/s/question/0D50O00003watlL/is-there-anybody-who-has-experienced-increasing-system-memory-while-playbackuser-sample-is-being-executed?s1oid=00D200000008Uid&OpenCommentForEdit=1&s1nid=0DB0O000000Kzmh&emkind=chatterCommentNotification&s1uid=0050O0000072hPK&emtm=1515401484370&fromEmail=1&s1ext=0
Since the sample works ok , I would debug this issue by simplifying the code until it looks like the sample code - as close as possible. E.g. take out code / thread handling as much as possible.
You could also check on other machines / OS / Languages / .Net versions - to see if that has an effect.