Labview memory full

[zalmay]

I am running window 2003 server on dell PE 2850 server. it is a domain controller.
when some programs ( Labview VIs ) run on this system, suddenly enormous large
file (run into GBs) is created in Labview 7.1/SysLog folde with format yyyymmddhhmm.log.

DSC module tells only about creation of this file, but is silent how to limit the size of this file.

when so much large file is creted , system memory is exhausted bcaz it canot accomodate

so much Huge file and "Memory is Full" error is appeared,  and system get hanged.

it is worthmentioning i have 4 GB RAM installed.

prompt response will b highly appretiated.

regards

[rolfk]

---

@zalmay wrote:

I am running window 2003 server on dell PE 2850 server. it is a domain controller.
when some programs ( Labview VIs ) run on this system, suddenly enormous large
file (run into GBs) is created in Labview 7.1/SysLog folde with format yyyymmddhhmm.log.

DSC module tells only about creation of this file, but is silent how to limit the size of this file.

when so much large file is creted , system memory is exhausted bcaz it canot accomodate

so much Huge file and "Memory is Full" error is appeared,  and system get hanged.

it is worthmentioning i have 4 GB RAM installed.

prompt response will b highly appretiated.

regards

---

You are aware of the fact that Windows 2003 Server is not supported by LabVIEW in any way? It may work but the reason it is not supported is because there have not been many tests and also there are known strange problems under certain circumstances.

Rolf Kalbermatter

Message Edited by rolfk on 01-23-2008 09:45 AM

[parthabe]

Have you checked the compatibility issues regarding LV-DSC with  Windows Server 2003 edition?

Just a side thought...

[falkpl]

Have you reproduced this on other versions of windows.  Often when I see an out of memory issue it is a simple codeing mistake with loops.  An unbounded loop with an autoindexing out array will very quickly take up any amount of memory.  Did you check the code to debug the source of the memory leak?

[CarlaU]

Hi zalmay,

I have been looking into your question and Rolf is correct. LabVIEW is not officially compatible nor is it supported on Windows 2003 Server or Windows 2000 Server Edition. It may or may not work since there has not been much testing done with LabVIEW on either of these operating systems. Supported operating systems can be found in the release notes for LabVIEW.

When exactly do you get this error? Is it when you run a specific VI or does it occur with every VI you run? If it is one particular VI, then you should look at the programming architecture of that VI and see if it causing a memory leak.

I hope this helps!

[EWTech]

I suggest NI get on this. We have and use a server for the usual stuff but it's also a database and data collection server. Servers have lots of advantages for enterprise applications. Server processes do not have GUI components and that's one of the reasons I won't le LV anywhere near my servers. If there was a way to use LabVIEW and it's associated driver set with the NI Fieldpoints that we have no other access to other than through LabVIEW I'd like to hear it. It's a cFP18xx unit. Without LabVIEW its mostly useless.

[Hillary_C_E]

Hi EWTech,

There is some functionality with creating a DLL in LabWindows/CVI to interface with the FP. This is especially true for the cFP 18xx which is a network module. I'd recommend checking this document .

[EWTech]

Interesting. I haven't used that compiler since IIRC 1995 or so. You folks know about Visual Studio, right? I know some banks still use Delphi but I haven't seen C++ Builder used professionally in ages.

Bob

[rolfk]

---

@EWTech wrote:

Interesting. I haven't used that compiler since IIRC 1995 or so. You folks know about Visual Studio, right? I know some banks still use Delphi but I haven't seen C++ Builder used professionally in ages.

Bob

---

Yes, that post is from 2002 and LW CVI used to support four compilers for which it could create object file formats. Borland C++ Builder was one of them as was Visual C++, Symantec C and Watcom C. The latter because LW CVI for Windows 3.1 was created with it and its dos4G memory extender model, which allowed an application to use under Windows 3.1 the 32bit flat memory model that Windows 32bit introduced later.

Support for some of these compilers (Watcom/Symantec) was only years later removed but at least CVI 8.0 still supports Borland C/C++ and Visual C/C++. Guess you still could get it somewhere.

Incidentially, LabVIEW, LabWindows CVI and just about anything else from NI for Windows 32 and 64 bit is compiled with Visual C/C++, so I'm sure the guys at NI do know Visual C/C++ quite well 😉

Rolf Kalbermatter

[EWTech]

OK then I should be able to find a DLL that provides access to the cFP-1808 that we have here. The document that was pointed to above is very short on specifics. I assume that this is documented in CVI. It looks like I'll have to create a linking native DLL to other assemblies to use this. Since we have a copy (not yet installed) of that part of the suite I'll have to install it and go from there.