Current Position:Home > Fatal Internal Error MemoryManager.cpp

Fatal Internal Error MemoryManager.cpp

Update:11-30Source: network consolidation
Advertisement
I've created a sequence file in teststand that uses the sub vi's for
reading out config files. If I run this on my development machine
there is no problem.
I tried to deloy everything onto a new target machine. I start to run
the sequence and i'm able to execute the 'Open Config Data.vi'. The
next step is to read out some data with the vi 'Read Key(String).vi'
but this creates the error. I get a Fatal Internal Error :
"MemoryManager.cpp" , line 406 LabVIEW 8.5.
What could cause this problem?

The Best Answer

Advertisement
I have been struggling with this error today. It appears that under some circumstances LabView does not automatically recompile all VIs requiring referencing a typedef when the typedef is changed. In my case, the problematic routine was one in which the typedef did not appear as a control, indicator or diagram constant. An array of the typedef was an output from one SubVI that was an input to another. The first routine had a case structure around it with some cases where the output took a default value. I assume the default typedef output is the core of the problem in my case. Manually recompiling the routine (or making any code changes to it) solved the problem.
One could probably do a mass recompile of the whole VI hierarchy to solve this problem, but that's undesirable in a large program that is being developed by a team. It is at least something to try if you are running into this error.
Unfortunately I have not been able to make a simple program that reproduces this problem. I have attached some code but it does not make LabView crash. However, bad pointer dereferences are tricky things to debug because the severity depends on where you end up when you dereference. (In my production code, LabView was trying to read location 0xFFFFFFFF; Windows killed it). So this example could be causing silent corruption. Or my suspicions could be ungrounded and the bug may lie elsewhere.
I do notice that when I change the typedef and quit labview, labview offers to save the TLVI and the two subVIs that contain the typedef control, but not the routine I suspect is causing the problem. ("Routine that doesn't recompile.vi" in my example.)
This message is related to support issue "Reference#7184406".
-Rob Calhoun
Attachments:
MemoryManagerCrash.zip ‏36 KB
  • Fatal Internal Error MemoryManager.cpp Update:11-30

    I've created a sequence file in teststand that uses the sub vi's for reading out config files. If I run this on my development machine there is no problem. I tried to deloy everything onto a new target machine. I start to run the sequence and i'm abl

  • Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph Update:10-11

    NOTE:  This IS a duplicate post from the Breakpoint.  Text slightly changed.  The post in Breakpoint can be deleted.  All comments should be placed in this thread. I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to

  • I have encountered the new error "Fatal internal error fpinit.cpp line 7398 Update:11-30

    I get the error message "Fatal internal error fpinit.cpp line 7398". I use:  TestStand 2.0 LabView 7.1 Vision 7.1 uEye USb Camera I've included into my TestStand programm some new steps that control the uEye USB Camera. I use following steps (al

  • Receive "Fatal Internal Error: Linker.cpp, line 1926 when run executable. Update:11-30

    Hi, I use invoke node to call multiple subvi.vit, it work fine under .vi but when run under an executable I receive this error: Fatal Internal Error: 'linker.cpp", line 1926 LabVIEW Version 7.0 You will lose any unsaved work. For more assistance in r

  • Fatal Internal Error : "OMUDClassMgr.cpp". Line 1128 Update:11-30

    I received the following message: Fatal Internal Error : "OMUDClassMgr.cpp", 1128 LabVIEW version 8.2.1 I was trying to build an application using the application builder. Has anyone else had this issue?  What needs to be done to fix this.Hello,

  • Can somebody fix my corrupted subvi, error "Fatal Internal Error" "objheap.cpp" Update:11-30

    Hello, I have been strugling to open this file after a reboot due to not responding computer. The file is a part a larger library however, this is the part that is not responding and giving "Fatal Internal Error" "objheap.cpp" .  Does

  • Fatal Internal Error : "LinkObj.cpp Update:11-30

    Hi, I currently upgraded the system from labview 8.0 to labview 8.0.1 and did a mass complile. However after doing that I am getting an error message reading "Fatal Internal Error : "LinkObj.cpp", line 587" everytime I close a particul

  • "Fatal internal error:"memory.cpp",line 593" Update:11-30

    I need some help. Can some please explain what i am doing wrong here. i have created a Dll from a LV 7.0 vi. The header file looks something like this: typedef struct { long dimSize; double elt[1]; } TD2; typedef TD2 **TD2Hdl; typedef struct { double

  • Fatal Internal error: "oleautomgr.cpp", line 2832 Update:11-30

    Hi, I have a program developped with LV 8.2.1. Now I have import this application with LV 8.5; if I run the VIs in Labview it works; when I run my program (executable version) I got this error "Fatal Internal error: "oleautomgr.cpp", line 2

  • Fatal Internal error: "oleautomgr.cpp", line 2832 when sending data by means of ActiveX methode Update:11-30

    I have experienced  error "Fatal Internal error: "oleautomgr.cpp", line 2832" during sending data to CAN card IXXAT iPCI-I XC16/PCI. LabVIEW communicates with that card by means of ActiveX methodes via "VCI Wrapper" which is