Fatal Internal Error : "LinkObj.cpp

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 particular sequence in TestStand. This error never used to occur before the update.
The error seems to occur when it tries to unload a particular VI which I use to add tasks in MAX.
I have tried repairing Labview but the problem still exists.
I would appreciate any help
Kewal
Attachments:
error message.JPG ‏15 KB

OK, now it's getting comical... 
I removed the second mathscript node from clasclap.vi and created a dummy LV math operation to replace it.  Called the new vi clasclap_part.vi (attached) and added it to the project in place of clasclap.vi.  Built the dll as usual.  BTW, I'm using the standard calling convention here, not the C language convention.
RESULTS: All of the called functions return zeros, even clasclap_part.vi.  But some good news: the dll isn't crashing Visual Studio anymore.
Now I'm realizing that the functions returning zeros issue greatly overshadows the reason I originally started this thread.  If I don't get any response, I'll start an independent thread that someone might take an interest in....
What might be helpful here would be if someone could (hopefully easily) take the summer .vis and the clasclap_part.vi and build their own dll.  Then, try to call it from VB6 and/or any other language or compiler.  What do you get?
(FWIW, I never mentioned that I'm not a fan of VB or Visual Studio.  LabVIEW is far superior IMHO)
Here is the revised VB code which calls the dll:
Private Declare Function Summer Lib "summerlib" (ByVal a As Long, ByVal b As Long) As Long
Private Declare Function Mathscriptsummer Lib "summerlib" (ByVal a As Long, ByVal b As Long) As Long
Private Declare Function Doublesummer Lib "summerlib" (ByVal x As Double, ByVal y As Double) As Double
Private Declare Function Clasclap_part Lib "summerlib" (ByVal x As Double) As Double
Sub Form_Load()
Dim x, y, fx As Double
Dim a, b, sum As Long
a = 1#
b = 2#
x = 1.2345
y = 2.3456
fx = 1
sum = Summer(a, b)
fx = Doublesummer(x, y)
sum = Mathscriptsummer(a, b)
y = Clasclap_part(290.01)
End Sub
Thanks,
Ted
Attachments:
clasclap_part.vi ‏276 KB

Similar Messages

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

    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 insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..  
    I have an existing graphs (qt 6) which originally had 2 cursors.  This occurred while trying to add the third cursor. 
    Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while.  However, I do recall seeing this problem when creating the original cursors, but not to this extent.  Plus I don't remember the original error message from that time.
    I needed to add one more cursor to the existing graphs.  As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message.  Tried it 3 times, same result.
    Here are the steps:
    Shut down the PC, went for a coffee, rebooted the PC.  Opened the LV project, opened the VI.  Immediately went to the graph properties to add the new cursor by doing the following steps: 
    Right click graph indicator icon on block diagram.
    Select Properties.
    Click on cursor tab.
    Click on Add
    Select Cursor 2 (3rd one, newly created)
    Change color
    Select cursor as a line
    Remove checkmark for "show cursor"
    Click OK
    I need to do this to 3 other graphs, same steps.  And as soon as I get to the step before clicking OK, I get the error message. 
    I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties).  But I've had this problem before when creating the first two cursors.
    Is it a bug?  Anyone else seen this?  Using LV8.2.  And the message is right about LOOSING ALL unsaved work!!!! 
    Here are more observations:
    Tried creating a new one on the second graph.  As soon as I clicked on the color, it crashed!
    See the error explanation below.  It is really clear, now anyone can solve it    LOL!!...  According to the error log, there's a bad image out there  
    .\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
    $Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
    0x007A81E8 - LabVIEW <unknown> + 0
    0x007A7BDB - LabVIEW <unknown> + 0
    0x00829D74 - LabVIEW <unknown> + 0
    0x008546CD - LabVIEW <unknown> + 0
    0x00C054E6 - LabVIEW <unknown> + 0
    0x0081B9C8 - LabVIEW <unknown> + 0
    0x0081EB9A - LabVIEW <unknown> + 0
    0x0084D9D4 - LabVIEW <unknown> + 0
    0x00854663 - LabVIEW <unknown> + 0
    0x00C054E6 - LabVIEW <unknown> + 0
    0x0085F7A1 - LabVIEW <unknown> + 0
    0x00BBACDD - LabVIEW <unknown> + 0
    0x00C06A2F - LabVIEW <unknown> + 0
    0x0085AA46 - LabVIEW <unknown> + 0
    0x00C06A2F - LabVIEW <unknown> + 0
    I observed the title bar after making changes to the properties.  I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes".  Saving was also much slower than usual.  I suspect, the program never got to placing the star before saving occurred.  However, I am noting everything.
    After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
    Does anyone have a clue at what causes this?   Has anyone seen this before?
    Thanks,
    RayR

    Hi Donovan,
    I can't remember seeing this elsewhere.  When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps. 
    I will let you know if I see this in the new vi.
    Thanks!
    RayR

  • I have encountered the new error "Fatal internal error fpinit.cpp line 7398

    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 (all steps written in LabView):
    - Initialze Camera
    - Wait
    - Close Camera
    - Wait
    I have the settings "Load dynamically" in TestStand"
    If I use also the setting "Unload  after sequence executes" and start the sequence I get somtimes a LabView error after running the Step for the Camera initialization. LabView is sometimes immediatlly closed. This happen at leased after 10 turns/starts of the programm. If I use the loop functions "Loop on selected steps" it happen only sometimes at the first loop. The initialize Camera Step is every time pass, if TestStand try to run the next step I get a error.( Sometimes I get also the message ActiveX Server got lost)  
    I detected also that sometimes in this case a constant in a other vi is emty. 
    Normally I use the setting "Unload  when sequence file is closed" then I have the problem only sometimes at the first turn.
    If the initialize Camera step is succesfull I have no problem with further camera steps.
    Regards
    Alexander
    Attachments:
    lvlog02-18-10-09-34-10.txt ‏1 KB
    Copy of Error.jpg ‏76 KB
    Copy of Error2.jpg ‏42 KB

    Hi Alex,
    I'd suggest to replace all ctl. with new ones.
    Perhaps one of them is corrupt.
    You will find a documentation about preferred execution system
    in the LabVIEW help. I also attached this files.
    Regards
    DianaS
    Attachments:
    help1.gif ‏37 KB
    help2.gif ‏11 KB

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

    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 resolving this problem, please relaunch LabVIEW, or contact National Instruments.
    Any suggestion will be very appreciated

    Hi David,
    What you are seeing is a known issue when calling LabVIEW 7.0 VITs from
    an executable or DLL if the VITs include any Express VIs. It can happen if you
    try to load
    multiple instances of that template VI using VI Server.
    There are a couple of workarounds for this issue:
    Take
    all the express VIs that are inside the template VI and turn them into
    static subVIs. You can do this by right-clicking on the express VI and
    selecting "Open Front Panel"; then save the express VI as a normal
    subVI.
    Build the entire application into a single executable, which will force all of the express VIs to get compiled as static subVIs.
    Don't use the runtime engine at all and always run your application in development mode.
    Let me know if the workarounds fix your issue, thanks.
    Good luck!
    - Philip Courtois, Thinkbot Solutions

  • Fatal Internal Error : "OMUDClassMgr.cpp". Line 1128

    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,
    This was reported to R&D (#4ALB7O89) for further investigation.  Are you able to reproduce this problem with the same VI?  Are you able to build an application with a simple VI?
    Regards,
    Elizabeth S.
    Applications Engineer
    National Instruments

  • Can somebody fix my corrupted subvi, error "Fatal Internal Error" "objheap.cpp"

    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 anyone know how to fix this issue or how to repair this file.
    I am using a LabView 2012.
    Thank you for your time.
    Attachments:
    Corrupted.llb ‏149 KB

    Hi obarriel,
    that could be a tricky job as LV2013 claims "block diagram can't be opened"!
    Meanwhile you should learn two things:
    - using LLBs isn't recommend practice nowadays (atleast not for storing daily work VIs)
    - make a backup of your works on a regular basis (using SVN/GIT is recommended too…)
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Fatal Internal Error MemoryManager.cpp

    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?

    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:"memory.cpp",line 593"

    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 f0;
    double df;
    TD2Hdl magnitude;
    } TD1;
    void __cdecl Spectrum(double freq, double amp, TD1 *Spec);
    And i have the following code where i allocate memory and attempt to call 'Spectrum':-
    TD1 *Power;
    double frequency=10, amplitude=1;
    Power = (TD1 *) malloc(sizeof(TD1));
    (*Power).magnitude = (TD2**)malloc(sizeof(TD2));
    *(*Power).magnitude = (TD2*)malloc(5000*sizeof(TD2));
    (*Power->magnitude)->dimSize = 5000;
    for (i=0; i<500;
    i++) {
    (*Power->magnitude)->elt[i] = 0;
    Spectrum(frequency, amplitude, Power);
    I keep getting Fatal internal error: "memory.cpp", line 593" when it tries to call Spectrum. I believe i have allocated memory correctly although i may be wrong. (I was getting 'exception' errors before). The VI i used to create the Dll contains a basic 'Function Generator' (sine wave) and a 'Power Spectrum'.
    I have looked at the Knowledge base and dll examples that come with LV 7.0 and have tried setCINArray and NumericArrayResize but have not had any luck. It seems like the documentation is for LV 6.0 and 6.1.
    Has anybody seen this or have any idea why i am getting this?
    Thanks

    > 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:
    >
    > double frequency=10, amplitude=1;
    > Power = (TD1 *) malloc(sizeof(TD1));
    > (*Power).magnitude = (TD2**)malloc(sizeof(TD2));
    > *(*Power).magnitude = (TD2*)malloc(5000*sizeof(TD2));
    >
    > (*Power->magnitude)->dimSize = 5000;
    >
    > for (i=0; i<500; i++) {
    > (*Power->magnitude)->elt[i] = 0;
    > }
    >
    > Spectrum(frequency, amplitude, Power);
    >
    > I keep getting Fatal internal error: "memory.cpp", line 593" when it
    > tries to call Spectrum. I believe i have allocated memory correctly
    > although i may be wrong. (I was getting 'exception' errors before).
    > The VI i used to create the Dll contains a basic
    'Function Generator'
    > (sine wave) and a 'Power Spectrum'.
    > I have looked at the Knowledge base and dll examples that come with LV
    > 7.0 and have tried setCINArray and NumericArrayResize but have not had
    > any luck. It seems like the documentation is for LV 6.0 and 6.1.
    >
    It looks to me like you are constructing arrays to pass to LV using
    malloc, instead of the labview.lib functions for creating or resizing LV
    array handles.
    You should refer to the manual on Calling External code for details on
    the construction of an array.
    Greg McKaskle

  • Fatal Internal error: "oleautomgr.cpp", line 2832

    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 2832"
    I got the error after I  open a Diadem connection.
    Another information: first time I have import the program in LV 8.5 and I have save the prj, LV ask me to overwrite all the VIs of the "Diadem addons". (Diadem connectivity); so I have uncheck "read only" in Diadem.llb and I have save the Vi.
    Someone can help me?
    Thanx a lot

    For the community's future reference, this issue was resolved by the customer calling in for support, at which time it was determined that a Mass Compile of the VIs was necessary to eliminate the error. The process to mass compile is described here.
    -Sam F, DAQ Marketing Manager
    Learn about measuring temperature
    Learn how to take voltage measurements
    Learn how to measure current

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

    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 COM object interface. Mass compiling of the project does not help. Card is initialized and configured propely. The driver card is working propely.
    LabVIEW version is 8.5
    The efect of that error is that labview completly shot down.
    I appraciate any suggetions
    thanks a lot

    Hello,
    Please try to reinstall the drivers for the CAN card, then make sure you close all references to the ActiveX control (at all levels) using the Automation Close primitive in LabVIEW.
    Regards,
    Emil

  • Fatal Internal Error "table.cpp" line 5117

    Using a table in a vi running within a sub-panel. The vi works correctly when run from LV but not when put in the sub-panel. I have the number of rows set to 18 and when I enter more data into the table (beyond 18 rows) LV locks up and produces the message.

    Sorry... I should have provided more information. I'm using LV 7.1.1. What I have is a SubPanel that contains a Tab Control. On one of the tabs I have a Table (control) with several rows visible. If I enter data into the visible rows, down to the last one, the vertical slider becomes visible. If I click on the slider to make more blank rows visible and then add some data into the next available row, LV locks up and gives me the fatal error message. I have attached a simple vi that duplicates the error I see in my program. After unzipping, run the Main.vi. Thanks for your interest!

  • FATAL INTERNAL ERROR 'datamgr.cpp', line no. 1882

    I am getting the above error when i try to create DLL for my vi. My vi transmits message from serial port to FPGA Module (ver 1.0). FPGA receives the message and stores it in the memeory, it is same as it is in the NI LVRT FPGA SERIAL READ.LLB. AS i create the dll and build it i am getting this error. Please help me out in fixing the error.
    I am using LabVIEW version 7.0
    Regards
    Subramania Bharathi

    Hi,
    Thanks for your curiosity in replying my questions. I am really sorry for replying so late. Actually the problem was with the NI SWITCH 2503 functions. Actually i was multiplexing the channels of my customized serial port using NI Switch module. This switching is done before i start my communication. My VI follows a sequence as follows.
    1. Connect two channelss using Switch functions
    2. configuration of both FPGA and the customized port
    3. Transmit data from the port
    4. Receive it in FPGA.
    5. Reset the channels using Switch functions
    I never expected that the error was because of NI Switch. When i removed them from my VI i was able to create the DLL and able to create sequence successfully to run in
    the Testsand. And further i am using Switch Executive for swithcing the channels in TestStand.
    But now i am very curious why it posted me that error when i used my NI Switch function?? I tried to create DLL for a VI that switches two channels and i was successful. But the error occurs only when i combine i with my FPGA functions!! If you could trace out the reason, please let me know
    Once again thanks a lot for your support
    Regards,
    Subramania Bharathi

  • Fatal internal error: "memory.cpp" line 638

    I have created a dll (C++) from a labview vi (7.1.1 WinXP) that does order analysis. However when i try to use this dll i keep getting this memory error. I believe i am allocating memory correctly (i.e. i am using DSNewHandle and DSSetHandleSize etc).
    I have seen other messages that claim that this error is caused by the "Type cast" function in LV. I don't use the "Type cast" function in my vi specifically (attached) however it is in some of the NI vi's that i use for order analysis (e.g. New Gabor Refnum.vi). The actual Labview code (i.e. the Labview vi that i used to create the dll) does not give me this error when i run it. It only occurs when i run the dll.
    Any help would be appreciated.
    Thank you
    Attachments:
    OrderAnalysis.llb ‏74 KB

    Forgot to mention that it does not create a failure when it happens. I have attached the build file that i used to create the dll and i have pasted my c++ code to verify that i am allocating memory correctly. Thanks
    long PulsesPerRev=0, *pDataSize, ErrorCode=0, Size=0, Speedlen, Timelen;
    double SampleRate=0, Value, MinOrder=0, MaxOrder=0, OrderResolution=0;
    double RpmOffset=0, RpmMult=0, QntOffset=0, QntMult=0, OrdOffset=0, OrdMult=0;
    float VibValue, TachValue, SpeedProfileRPM, SpeedProfileTime;
    int32 i=0, j=0, k=0;
    unsigned short int iWindowType, iActWinType = 0;
    int iInstance, iWindowLength, iActWinLen = 0, NumofSamples=80000, nrows =2000, ncols = 2000;
    TD1Hdl HdlData, HdlTach;
    TD2 InputWinInfo, ActualWinInfo;
    TD3 OrderRange;
    TD4Hdl HdlSpecMap; //Spec Map (intensity plot data)
    TD5Hdl HdlSpeed, HdlTime;
    TD6 RpmScale, OrdScale, QntInfo;
    // Set values
    InputWinInfo.windowLength = iWindowLength;
    InputWinInfo.windowType = iWindowType;
    // Set values
    ActualWinInfo.windowLength = iActWinLen;
    ActualWinInfo.windowType = iActWinType;
    // Set values
    OrderRange.MinOrder = MinOrder;
    OrderRange.MaxOrder = MaxOrder;
    OrderRange.Resolution = OrderResolution;
    OrdScale.multiplier = OrdMult;
    OrdScale.offset = OrdOffset;
    RpmScale.multiplier = RpmMult;
    RpmScale.offset = RpmOffset;
    QntInfo.multiplier = QntMult;
    QntInfo.offset = QntOffset;
    // Allocate memory for spectral Map
    HdlSpecMap = (TD4Hdl) DSNewHandle(sizeof(TD4Hdl));
    error = DSSetHandleSize(HdlSpecMap, sizeof(long)*2 + nrows*ncols*sizeof(double) );
    if (error != mFullErr && error != mZoneErr)
    (*HdlSpecMap)->dimSizes[0] = nrows;
    (*HdlSpecMap)->dimSizes[1] = ncols;
    else {
    AfxMessageBox("Unable to allocate memory");
    // Allocate memory for speed profile arrays
    HdlData = (TD1Hdl) DSNewHandle(sizeof(TD1Hdl));
    error = DSSetHandleSize(HdlData, sizeof(long) + NumofSamples*sizeof(double) );
    HdlTach = (TD1Hdl) DSNewHandle(sizeof(TD1Hdl));
    error = DSSetHandleSize(HdlTach, sizeof(long) + NumofSamples*sizeof(double) );
    Speedlen = 5000;
    Timelen = 5000;
    // Allocate memory for Vibration Data and Tach Data
    HdlTime = (TD5Hdl) DSNewHandle(sizeof(TD5Hdl));
    error = DSSetHandleSize(HdlTime, sizeof(long) + Timelen*sizeof(double) );
    HdlSpeed = (TD5Hdl) DSNewHandle(sizeof(TD5Hdl));
    error = DSSetHandleSize(HdlSpeed, sizeof(long) + Speedlen*sizeof(double) );
    // Alocate memory for data size
    pDataSize = (long *) DSNewPtr(sizeof(long));
    // Read in Data from file
    FILE *stream;
    char line[100];
    stream=fopen( "C:\\OrderAnalysis.txt", "r" );
    while (fgets( line, 100, stream ) != NULL)
    sscanf( line, "%f %f",&VibValue, &TachValue);
    (*HdlTach)->elt[i] = TachValue;
    (*HdlData)->elt[i] = VibValue;
    i++;
    fclose(stream);
    (*HdlTach)->dimSize = i;
    (*HdlData)->dimSize = i;
    OrderAnalysis(&HdlData, &HdlTach,
    &InputWinInfo, SampleRate, PulsesPerRev,
    &OrderRange, &ActualWinInfo, &HdlSpecMap, &HdlSpeed,
    &HdlTime, &RpmScale, &OrdScale,
    &QntInfo, pDataSize);
    Attachments:
    OrdAnalysis3.zip ‏2 KB

  • Fatal Internal Error : "ThEv​ent.cpp&qu​ot;, line 209

    Hi,
    Any help with the following AddRef()/Release() issue would be most appreciated: 
    I'm a software developer working on a COM (ActiveX) object for use by e.g. C# (test ok) and LabVIEW clients.  The object supports events; however, when events are accessed with the "Register Event Callback" block, LabVIEW does not free the object when the VI is finished, and upon subsequently closing LabVIEW, I receive the following dialog:
    Fatal Internal Error : "ThEvent.cpp", line 209
    LabVIEW version 8.6
    You will lose any unsaved work.  For assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
     and log:
    #Date: Fri, Nov 14, 2008 12:44:58 PM
    #OSName: Windows NT
    #OSVers: 5.1
    #AppName: LabVIEW
    #Version: 8.6
    #AppKind: FDS
    #AppModDate: 06/26/2008 05:25 GMT
    source\mgcore\ThEvent.cpp(209) : DAbort:
    $Id: //labview/branches/Saturn/dev/source/mgcore/ThEven​t.cpp#6 $
    0x00B129F6 - LabVIEW <unknown> + 0
    0x0040F5C0 - LabVIEW <unknown> + 0
    0x7719C351 - OLEAUT32 <unknown> + 0
    0x7712DB25 - OLEAUT32 <unknown> + 0
    0x77EF658C - RPCRT4 <unknown> + 0
    0x77EF4BF3 - RPCRT4 <unknown> + 0
    0x7717E724 - OLEAUT32 <unknown> + 0
    0x77600C31 - ole32 <unknown> + 0
    0x77600BDB - ole32 <unknown> + 0
    0x7750F237 - ole32 <unknown> + 0
    0x7750F15C - ole32 <unknown> + 0
    0x7750FC79 - ole32 <unknown> + 0
    0x77600E3B - ole32 <unknown> + 0
    0x776009BC - ole32 <unknown> + 0
    0x77600DF2 - ole32 <unknown> + 0
    0x7750FCB3 - ole32 <unknown> + 0
    0x7750FAE9 - ole32 <unknown> + 0
    0x7E418734 - USER32 <unknown> + 0
    0x7E418816 - USER32 <unknown> + 0
    0x7E4189CD - USER32 <unknown> + 0
    0x7E4196C7 - USER32 <unknown> + 0
    0x0041E852 - LabVIEW <unknown> + 0
    0x0042AB32 - LabVIEW <unknown> + 0
    0x00A27592 - LabVIEW <unknown> + 0
    0x00A2DC60 - LabVIEW <unknown> + 0
    0x00E3A5B9 - LabVIEW <unknown> + 0
    0x008F0FF6 - LabVIEW <unknown> + 0
    0x008F0CDA - LabVIEW <unknown> + 0
    0x008F0EFB - LabVIEW <unknown> + 0
    0x008F0F40 - LabVIEW <unknown> + 0
    0x015AB20D - LabVIEW <unknown> + 0
    0x7C816FD7 - kernel32 <unknown> + 0
    0x00000000 - LabVIEW <unknown> + 0

    I've attached a minimal COM server (that starts a thread when events are requested) that shows the issue.  Steps to reproduce with LabVIEW 8.6 on Windows XP for x86 follow(stuff in parenthesis are comments):
    (1) unzip HelloClass.zip to C:\ (4 files:  hello.vi, callback.vi, HelloClass.dll, Hello.tlb)
    (2) C:\>regsvr32 helloclass.dll (should get "DLLRegisterServer in helloclass.dll suceeded." dialog)
    (3) C:\>hello.vi (start LabVIEW)
    (4) Ctrl+R (run the VI.  You should see "Command: test" in the String Indicator.  At this point the last call into the server is AddRef() but should be Release())
    (5) Alt+F4 (close the VI)
    (6) Alt+F4 (close LabVIEW)
    You may need to perform steps 3-6 up to ~10 times, because at this point one of 3 behaviors randomly occurs:
    (A)  Fatal Internal Error : "ThEvent.cpp", line 209
    (B) Release() is finally called the same # of times as AddRef(), causing the destructor ~HelloClass to run (which kills the thread).  This should instead happen after step 4 (which it does if you remove the "Reg Event Callback" block)
    (C) Release() is called several times, but not enough to decrement the reference count to 0
    Behavior A doesn't occur if the server doesn't start the thread.  In source.zip, I've also attached the server's source code for your R&D team along with dbgMon, which is useful for looking at the _RPTF debug output.  Thanks much for your patience and for looking at this.
    Attachments:
    HelloClass.zip ‏84 KB
    source.zip ‏173 KB

  • Fatal Internal Error : "objheap.c​pp", line 579 - Labview 7.1 running on vista

    Hello,  
    I was developing a project in Labview 7.1 and had saved it on vista when the vista OS decided to enter suspend, Labview 7.1 stopped responding as a result and I had to reboot. I will never trust vista again but when I try to open the VI I get the following error:
    Fatal Internal Error : “objheap.cpp”, line 579.
    And the following text file report is created. What I am wondering is there any way to restoring or uncorrupting this VI which is attached. Sub VI’s are not included but if you can get the VI to open even without them then the problem is sorted.
    #Date: 25 Feb 2009 12:13:28
    #OSName: Windows NT
    #OSVers: 5.1
    #AppName: LabVIEW
    #Version: 7.1
    #AppKind: FDS
    D:\lvmerc\src\source\objheap\objheap.cpp(579) : DAbort: Heap has insane block size
    $Id: //labview/branches/Mercury/dev/source/objheap/objh​eap.cpp#3 $
    0x009DFC85 - LabVIEW <unknown> + 0
    0x007080AC - LabVIEW <unknown> + 0
    0x007079E1 - LabVIEW <unknown> + 0
    0x00A66716 - LabVIEW <unknown> + 0
    0x00706B02 - LabVIEW <unknown> + 0
    0x006073AE - LabVIEW <unknown> + 0
    0x0070532B - LabVIEW <unknown> + 0
    0x00A653E5 - LabVIEW <unknown> + 0
    0x00A66911 - LabVIEW <unknown> + 0
    0x009ED231 - LabVIEW <unknown> + 0
    0x005ADED7 - LabVIEW <unknown> + 0
    0x004B7F79 - LabVIEW <unknown> + 0
    0x004B7EA7 - LabVIEW <unknown> + 0
    0x004B7CF9 - LabVIEW <unknown> + 0
    0x004B8492 - LabVIEW <unknown> + 0
    It also managed to corruptly my library file for the project which I cannot open also and is attached,
    Thank you
    Message Edited by Support on 03-02-2009 08:50 AM
    Attachments:
    looptest.vi ‏1743 KB
    AbbottHMITree.llb ‏4063 KB

    Hello Paul,
    I have been looking into your error code as well as the attached files of your VI and LLB.  Pasting in your error code is proving very helpful in trying to help you.  I initially tried to open your files in my system, where I would possibly be able to resave them for you, however it looks like I will have to try a different approach.
    As I understand it, you have been using LabVIEW 7.1 Full Development System with Windows Vista.  LabVIEW 7.1 was released during the years when only Windows 2000 and XP were available.  With the release of Windows Vista in later years, National Instruments produced LabVIEW 8.2.1 with support for Windows Vista Business or greater. 
    Please reply with the following information:
    Are you using Vista 32-bit or 64-bit?
    Are you still able to open the LabVIEW Development Environment to produce new VIs?
    Have you tried to open other VIs (after backing them up) with LabVIEW 7.1?
    Regards,
    George T.
    Applications Engineering Specialist
    National Instruments UK and Ireland

Maybe you are looking for