performance

[analog]

Hi,
I have a 4647KB LabView Application running on a laptop (498MHz, 384MB of RAM, 768 MB of Virtual Memory). This application would run and then crashes in the middle and give me a blue screen, and the computer would restart itself. But smaller application about one fourth of the size (1000KB or so) works fine. Does this mean I need more RAM or something? I pull up the task manager and performance is about 30% or less, unless it needs to open a spread sheet, then performance goes to 100%, but then it goes back down to like 5%-30%.
Thanks

[altenbach]

I don't think the application size is a big issue. More important is the allocated memory for data, etc. while running. Have you tried any profiling?

Im my experience, LabVIEW usually deals gracefully with issues and does not crash easily. What kind of application is this? Does it include dll calls or third-party drivers? Waht is your LabVIEW version?

[analog]

No, I have not try the profile VI, if that is what you are referring to. This is a main VI that calls several other sub-VI dynamically. Each sub-VI will ran in the order that the user specified; each sub-VI is a different test function. There is a third-party DLL, but it got pass the point of calling that DLL and actually crash when running one of the sub-VI.

[analog]

OK, I think I found my problem. I forgot to close one of the references. But now at the end, when I go to exit everything, every reference should be closed at this point in the code. I get a blue screen, and real quick it says "dumping of physical memory or something", and the computer restarts itself. Anyone has run into this problem before?
Thanks

[rolfk]

analog wrote:

> OK, I think I found my problem. I forgot to close one of the
> references. But now at the end, when I go to exit everything, every
> reference should be closed at this point in the code. I get a blue
> screen, and real quick it says "dumping of physical memory or
> something", and the computer restarts itself. Anyone has run into
> this problem before?

Sure and the only way I know of creating such in modern W2K or XP
systems is to call into buggy DLLs who most preferably call into device
drivers at some point. A DLL alone only working in user mode almost
never has the capability anymore to create a BSOD. And if you stay in
LabVIEW alone you really have to do some serious things to even get it
to crash at all.

Ro
lf Kalbermatter