Are there any tricks or switches, which can be used to maximize the amount of a single memory chunk that can be allocated by code run as Teststand Teststep ? Background for that question: We have observed that a testroutine run in a Teststand CVI code module shows that you can allocate as maximum a block of about 250MB size ( That means malloc() calls with bigger sizes will fail) when Windows Tastmananager still showing 600 MB of free physical memory. And that maximum size doesn't change even if we put 512MB additional physical memory into the machine,which is running Teststand . However at the same time ( Teststand running and stopped by breakpoint in the CVI code module ) a standalone CVI program using the same testroutine is able to allocate a 1GB chunk . So it seems that neither Windows nor CVI restricts that maximum size but Teststand is the culprit.

Replying myself: After using the imagecfg.exe utility on seqedit I can see with vmmap an additional 900M chunk of free space, which seems to solve the allocation problems. And I didn't see the UI issues so far.

NI TestStand

memory allocation within TestStand teststeps

Solved!

Author

Thanks for the info. Now,if I stumble over one of these issues, I don't need to search for the reason.

Message 11 of 11

(809 Views)

NI TestStand

memory allocation within TestStand teststeps

Re: memory allocation within TestStand teststeps