TestStand 3.1 Report Memory Leak

[Tonythetiger]

Hi everyone,

I been looking at the memory usage of my TestStand code lately.  I noticed I have a memory leak with On The Fly Reporting using XML report file.  I'm currenlty using labview 7.1.1 and TestStand 3.1f for development.   I came about this program from seeing test station go to a snails crawl.  The program starts out around 100MB and will keep growing using up all the systems memory, the largest I seen was 500MB.   What is happening is the testers like to keep the on the fly report screen up during the test  and not view the execusion window.  At the end of each run the program will grow 10MB to 30MB.    I know the problem can be solved by turning off on the fly reporting, but I would like to try find a programing option first.

I have looked at the other forum entries about:

Turning off database collection

Editing  model options : ModelOptions.DiscardUnusedResults = True and Parameters.ModelOptions.NumTestSockets = 1

Adjusted the array size of the report to 300

None of the options seem to have worked for me, most the post say move to teststand 3.1 cause it an 3.0 issue.

I was wondering if there are any other options to try  in teststand, or any way to turn off/close IE to release memory between tests.

I'm currently running the code on Windows XP SP2 

IE6/IE7 depending on the test station

P4 or Centrino  with 512MB to 1GB of ram

The GUI window is a modifed  example of the basic VI EXE that calls teststand

The code is installed using labview and Teststand  deployment builders, so the test machine are using runtime labview 7.1.1  and runtime TestStand 3.1

Thanks to any one who can offer alittle extra help on the topic

[Song_D]

Hi, Tony,

Several questions for you:

1) Is it possible for you to post a simple sequence file (that doesn't require any hardware) that reproduce the error.
2) Does the leak occur with html or text report?
3) Do you get any error message?

It'll be the best if I can reproduce this on my end.

Song D

[Anand_Jain]

Hi
I know that you are generating HTML reports using on the fly reports.

To help reproduce you problem better I have a couple of questions.
1. Do you have a lot of failed steps in your sequence?
2. What do you mean by " I know the problem can be solved by turning off on the fly reporting, but I would like to try find a programming option first." - if you turn off on the fly reports do you not see the leak? Do you still have the report tab selected?
3. Do you see the leak if you do not show the report tab in the OI?
4. Are you using Test UUTs or are you creating a new execution for each UUT
5. can you append TestStandModelReportOptions.ini from the computer which shows the leak

Thank you
Anand Jain
National Instruments

[Tonythetiger]

Sorry guys thinks got  really busy here working on other projects I totaly forgot about  the message I posted.

The leak is happening with XML only, memory leaks happens with all xsl formats ( gains 20MB to 50MB a test)

Using HMTL/TXT for report, there is no leak at all ( gains a couple of MB a test)

I do not get any error messages when using this code.  Code been in production use for months now, I finaly having free time to investigate the high memory usage of the code for prolong periods.    I will say when looking at the execution Tab of the LabVIEW GUI using XML there isn;t a high memory leak. Though when the technician keeps the View on Reports using XML reports option the code jumps memory usuage increases rapidly.

I'll try to edit the teststand sequence to post.  Would you like  the LabVIEW Test GUI interface also?

[Tonythetiger]

Actually the reports are XML not HTML.

There are alot of pass steps, usualy after a couple of failed steps, the sequence will terminate.

The memory leak seem to exaggerated, since the technicians like to view the Reports Tab instead of Execution Tab when running program.  If the operator keeps the view on the execution tab during the program, the report screen is not being updated, so less memory is taken up.  Since the techs like to keep the report screen up during the entire test, the xml file constantly being update and  the program increases +50MB after the first run.   So turning off Reports on the fly, they can not view the report during the test and the memory usuage stays low.

I do not see a leak at all if I do not click on the reports tab,  and the leak seems to only happen with XML files, TXT and HTML reports do not cause a memory leak, even when viewed on the fly for the entire test.   I wanted to keep XML-expandable cause it easier to see what sequences failed then scanning through the entire report.

I'm using Test UUT call up the test.    The executable terminated if you press the exit button on the executable.  After test is finished, the standard Pass/Fail comes up then the standard  enter UUT serial number comes up.

I'm including the reports option INI  I use .

Thanks for you help in this matter, sorry being little late with replying. 

[Song_D]

Hi, Tony,

Are you still going to post a simple sequence file that can reproduce your problem. That will help troubleshooting the memory leak issue.

Song D