Fatal Internal Error: "Memory Manager.cpp", line 547

[pritam]

Hello,

I am using LV 2009 and I am also getting an error as follows:

=======================================================

Fatal Internal Error: "Memory Manager.cpp", line 547

LabVIEW version 9.0.1 

You will lose any unsaved work. For assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.

======================================================= 

I get this error when I start executing steps on TS 4.2.1 as well as when I do "Unload All Modules" in TS. Please find the attched logs. Further, I could not run anything in TS and need to restart the PC to re-run the sequence after everytime this error occurs.

We have transited through LV 8.0, 8.2, 8.5 and now 2009 over past 4 years for our project and this is the first time I could see this error.

Please help.

Thanks.

[muks]

See here

[pritam]

But I am not trying to save in any previous versions. I am simply trying to run the code in 2009 which has been developed in 8.5.

Thanks.

[ankitavarma]

Adding on to Pritam's post:

For the earlier "Fatal Internal Error: "Memory Manager.cpp", line 547" , we found that a couple of our dll's which were developed in LV 8.5.1 had not been recompiled in LV2009. After recompiling each of them in LV2009, and then running the same sequences in TestStand,this error vanished.

But now again we're seeing this error, and that too only on  3 PCs systems out of 5 PCs!

The same installer has been installed on all 5 sytems (after removing the earlier installers and running MSI Blast.exe them).

The error now appears again, only when we try to exit TestExec.exe and another tool built in LabVIEW.

So everything works fine and tasks are performed,etc, but when we close the window or try the exit that program, the "Fatal Internal Error: "Memory Manager.cpp", line 547" pops up.

If we say "OK" to it, the window closes, but the Task is seen still running in the Task Manager and has to be manually terminated (End Task).

Does anyone know what could be going wrong?