Veristand TDMS Log: Data Cache :: LabVIEW memory full

[rajamodol]

Hi Everyone,
Hi NI Expert,

I am using:
LabVIEW 2015 SP1
Veristand 2015 SP1
Teststand 2014 SP1
PXI-RT Chassis

Currently, i have an issue with TDMS logging. I am not sure if this is related to LabVIEW or Veristand, but i would just post it here. In case admin wants to move it, please feel free to do it.

Here is the situation:
1. I am developing GUI, which is based on Teststand Operator Interface.
2. GUI is responsible to open/execute any teststand sequence in a sequence file.
3. Teststand sequence  calls a vi to deploy Veristand RT-Sequence File, per each test case.
4. Teststand sequence  calls a vi to log (TDMS format) point #3 (parallel).

Here is the action:

1. I run a long-test, ca 5000 test cases which just a loop of point #3.
   It works without any crash and error.

2. I run a long-test, ca 5000 test cases by executing pointt#3 and point#4 (parallel as one case)
   GUI reports an error after sometimes (ca. after 200 test cases) and tells me:
   - LabVIEW Memory full.
   - StimulusProfileSessionService.lvlib:ECreateSessionDataCache.vi.ProxyCaller
   (See picture for more detail)

Here is the effect:
1. I can't deploy any RT-Sequence file to Veristand
2. When I open Veristand console viewer, I can't see my PXI. No connection.
   Facts: PXI is still working properly and said "awaiting for command"

Here what i have monitored during the test until "LabVIEW memory full" comes:
1. No memory leak detected from "LabVIEW Desktop Execution Trace Toolkit"
2. Everytime RT-Sequence is called and deployed, memory is increased but it will decreased again as i have released them.
3. To my understanding:
   LabVIEW has no issue of memory growth. there was a peak (up to 1.169GB), but stil under max 2GB.
   Veristand has no issue of memory growth. there was a peak (up to 1.268GB), but stil under max 2GB.

2 pictures are attached.

Here is what i have done:
As i thought, this is just issue from host pc,
1. Close veristand without undeploying current system definition.
2. Stop Test and Close GUI
3. Close LabVIEW
4. Windows logoff
5. WIndows logon
6. Start GUI and start Test
7. It works properly.

This issue is re-produceable.

My question:
Why this is occured ONLY when i do TDMS logging?
What is ECreateSessionDataCache.vi? Do i have to clean-up something there? If yes, how?
Any helps, support, would be very HIGHLY appreciated...

Thanks,

Rajamodol

[rajamodol]

Since nobody has reponded,

I will update my status:

- Using same Test System, same Veristand Project.

- After ca. 5 hours, test crash. I saw on Veristand Project Explorer, that i am not connected to the system.

- Once i tried to redeploy the same system definition, the following windows popped-up:

 

- So, still the same error:

The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:
Error 2 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi

Possible reason(s):

LabVIEW:  Speicher ist voll.
=========================
NI-488:  Keine Listener für GPIB gefunden.
=========================
NI VeriStand:  Eigenschaftsknoten (Arg :2)  in Voltage Scaling.lvlib:Compile Calibration Binary from XML.vi->NI VeriStand Server.lvlib:NI VeriStand Server.vi->NI VeriStand Gateway.lvlib:VeriStand Server Wrapper.vi

And this is what process explorer reported:

Why Veristand's private bytes is always increasing? Any idea how to clear / cleanup its unused memory?

Thanks,

Rajamodol 

Added:

I closed Veristand completely (takes some seconds), then restarted it, opened same project, deployed it.

It works. 

Test is resumed, and works well. BUT, once my GUI command to do TDMS logging, Veristand private bytes increased again.

[CPT-NI]

Hi!

Thank you for your forum post!

This issue has now become a Service Request and is being worked on with NI Applications Engineers.

Kind Regards,

C

[rajamodol]

Hi,

Thanks again for taking this issue. However, i am still waiting for the good answer.

Kind Regards,

Rajamodol