Problem with Report Generation in TestStand 3.0

[kawilso1]

While using On-the-Fly Test Report Generation capabilities in TestStand 3.0, the PC become very sluggish and occasionally there are error messages containing an error code of -17000 and the statment, "Out of Memory". The error dialog usually appears while attempting to run the "reportgen_html.seq" file. Do you have any suggestions as to how we may correct this problem?

[Nick_Storton]

Hi,

I have a few questions for you before I can attempt an answer.

1. How much memory do you have in the PC.
2. How many results do you think have been collected when you get this error.
3. Do you have any other applications running.
4. What code modules are you calling.

I will respond to your reply

Regards,

Nick

[kawilso1]

In response to your above questions:

1. The PC has 512 megs of RAM with about 10 gigs of space free on an 18.6 gig drive.
   
2. The test ran for 28 hours and 10174 results were collected.
   
3. We have an application running that was developed in-house. We have run it seperately from TestStand and have not encountered this problem.
   
4. We are mainly making calls to DLLs that interact with our application. The DLLs also access ComPorts and sockets on the PC.
   

[kawilso1]

In response to your above questions:

1. The PC has 512 megs of RAM with about 10 gigs of space free on an 18.6 gig drive.
   
2. The test ran for 28 hours and 10174 results were collected.
   
3. We have an application running that was developed in-house. We have run it seperately from TestStand and have not encountered this problem.
   
4. We are mainly making calls to DLLs that interact with our application. The DLLs also access ComPorts and sockets on the PC. In addition, we have observed this problem on steps not making calls to our DLLs.
   

[Nick_Storton]

Hi,

Just a couple more questions:-

1. How much memory do you have free before you run the test sequence but with everything loaded.
2. What report configuration settings do you have in Teststand. (i.e. what is included in your report).

Nick

[kawilso1]

In response to your questions:

1. With nothing open, we have 116 MB in use. With just TestStand and the sequence open, we have 133 MB in use. With the sequence being executed - but paused on the first step, we have 148 MB in use.
   
2. We have our report generation configured so that,
   
   
   
   • Step results are included ( Test Limits and Measurements ).
     
   • Execution times are included.
     
   • On-the-fly reporting is enabled.
     
   • The DLL report generator is being used.
     
   
   

[Anand_Jain]

Hi

The test which you trying to run could potentially be leaking memory. I would suggest that you do the following.

1. Run the tests without report generation and result collection. Monitor the memory usage of your test using either taskinfo2000 or PerfMon and monitor your application.

To turn off result collection go the configure-> station options-> general tab -> Check disable result recording for all Sequences.

To turn off report generation -> configure-> report options-> and check disable report generation

If you tests still give a out of memory error then potentially the tests are leaking memory. Also if you see an increase in memory usage when running your tests then you could potentially be leaking memory in the tests

If your application
does not give errors then I would turn on result collection and keep report generation disabled and check if you get errors.

If you get memory errors then you just might need more RAM to store all the results.

If you still do not get any errors then I would turn on report generation and result collection and set the report to txt. If you still do not get any errors.

If you get errors then you might just need more memory to generate the report and display it.


I hope this help

Regards

[kawilso1]

We have followed your above suggestions reguarding disabling the report generation and result collection features in TestStand to resolve the out of memory error we have been receiving. Please view the attached file for our comments and questions. We look forward to your feedback.

Thanks.

[Anand_Jain]

Hi
I have not read your word document completly but I would suggest that you contact NI support at www.ni.com/support and will be able to help you with your problem.
Regards

[silvius]

Hi,

I've processed this thread and I have an additional suggestion, as in the past we also experienced this "Out of Memory" error message during over-night testing.

We've managed to solve this problem by changing the Virtual Memory settings of the PC (running WindowsXP).
The best results where achieved by setting the 'Paging File Size' to 'System managed size' for the PC system drive and we ensured more than 1.5 GB free space on the system drive.

Hope this helps,

Regards,
Silvius