Error kernel.cpp line 144 on exiting an EXE

We have a distributed TCP/IP based control system in LV 6.1 running on W2K. Occasionally we have TCP read errors and when this occurs we end up having to reboot the application(s). We got the kernel.cpp 144 error when we exited out of one EXE. I cannot find any information on this error. Does anyone have any inof on this error? Causes? Things to check?
TIA, Mike Ashe

Hello Mike!
I have searched our internal databases here, and we do not have any documentation relating to the kernel.cpp error line 144.
When you get the TCP read errors, do you get error codes associated with those errors, or do your applications just freeze? Also, does this just happen when you are in the run-time (EXE) environment?
As of LabVIEW 7.0, there is an error report that is generated when LabVIEW experiences a *.cpp crash, and there are no reports of this line number in our databases, so it is possible that whatever problem exists in your application has been investigated and fixed in the later versions of LabVIEW.
If you have any more information I would be happy to look into it!
Regards,
Colin C.
Applications Engineering
National Inst
ruments
Colin Christofferson
Community Web Marketing
Blog

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

Internal error: "memory.cpp", line 593 with PXI 8175

Hi,
I have created a program with Labview RT 7.0 which makes acquisition, storage and display of data with PXI controllers 8175.
I used Datasocket for the data display on a deported computer.
Because of the number of the Datasocket tags used, instead of sending values all the time, I'm sending value for the deported computer only if the user needs to see it.
For example : if the user needs to see data, so only Datasocket tags for data display will be active, and if the user needs to see parameters values, so only parameters datasockets tags will be active. And, if the display program is in "standby" mode, almost all datasocket aren't active.
So when the user needs to see data values, he opens the data values window of the display program, and then, the datasockets tags for data value are now active, but : sometimes at this moment, the PXI stops with an "internal error "memory.cpp" line 593"!
The only solution is to manually reboot the PXI, the programmatically reboot doesn't work in this case of error. But it is far away from the displaying computer.
The error happens regularly after a 2 weeks period of standby. So I though about a memory overflow, I checked all the arrays, and none of them is growing to the infinity.
If someone knows about this problem, I will be very happy to learn about how to get rid of it!!!
Best Regards,
G Liagre
Best regards,
G Liagre

Hi Rob, Hi Matthieu,
Thank you for your reply.
I found in the database many reply about this error, but none of them were helpfull for me.
I tryed your link to the knowledge data base, but the error described there is for dll association in LabView and interface nodes.
I didn't used any interface node in my code.
The problem is that I cannot test my program on the PXI because I don't have access to it rightnow (only by remote desktop, and with a 56k modem..)
Let me give you a part of this huge code.
I suspect this part of the code to be the one which create the problem, but it's not sure.
If you find something obviously wrong, tell me!
Best regards,
G Liagre
Best regards,
G Liagre
Attachments:
Communication.zip ‏931 KB

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:"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

Stop labview application from MS VC got internal error: image.cpp line 11450

Hi:
I need to control a labview application (It's been compiled as exe file)from my MS VC program. I tried using PostMessage(hWnd, WM_CLOSE) from whithin my program as MSDN suggested method to stop an application
cleanly. However, when i put my program in debugging mode and run it step by step, the LV program generate an internal error "image.cpp linexxxx" after it reached that PostMessage() call. in run mode , the Labview app simply ignore the WM_CLOSE message sent from my program.
So is there any other ways to stop labview application from VC program?
Thank you!
ls

> So is there any other ways to stop labview application from VC
> program?
You can use ActiveX. Turn the server on for your built app, open a
connection from VC, and use the app or VI properties to get LV to exit.
Greg McKaskle

CS3 Encore: internal software error CGOPGrouper.cpp line 401

Start to build and get to "Planning navigation for movie" and this error occurs:
internal software error: .\Vobulator\TitlePlanner\CGOPGrouper.cpp line 401
I've done pref->media->cleaning database but it does not help.
I have 18 chapters in this timeline. Removing the last timeline seems to solve the problem.
Is this a known bug?
Thanks!

I have another project which has 24 chapters. The menu has 15 button linked to chapter markers. It builds fine.
The problematic one has a menu with 18 buttons.
Could this be the problem?

HELP! Installation error:fontObject.cpp,line 506

I can't install the 'j2sdk-1_4_2-nb-3_5_1-bin-windows.exe', Java 2 SE Platform 1.4.2 with NetBeans IDE 3.5.1
I get this error:"Assertion failed:errno==0 && count == (size_t) size,file
../../../src/share/native/sun/awt/font/fontmanager/fontobjects/fontObject.cpp,line 506"
How can I do, please help me~~~
THANKS.......

Erm, you don't say what your OS is...
Generally, most try to download and install SDK and NetBeans separately (in that order).

Fatal error splitpanels.cpp line 1148

I'm using LV 8.2.1 and I'm getting a fatal error. I've tried re-loacting my code in order to purge it, but to no avail.
The error message says "SplitPanels.cpp" Fatal error line 1148....
Any idea what's going on here?
It happens when I receive a double-click on one VI (located in a sub-panel of the main VI), relay a message to the main VI to replace the VI with another in the sub-panel.
There's a singlesequence of code which bombs LV. The same frame of my State maching can be called via other means without bombing, so there must be something in the background.....
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Unfortunately, I haven't found what I'm looking for there.
I'm not getting an unhandled error, I'm getting a Fatal error. I'm crashing LabVIEW.
I've simply disabled the particular part of code leading to this.....
It also crashes in 8.5.1.
Shane.
Message Edited by Intaris on 08-27-2008 09:02 AM
Say hello to my little friend.
RFC 2323 FHE-Compliant
Attachments:
Fatal arror Line 1148.png ‏6 KB

Fatal error (graphobj.cpp line 56 ) when opening a vi

I cannot open my vi. Labview reports a fatal error and exits. Any workaround?
Log file:
#Date: Tue, Oct 05, 2004 11:17:20 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.0
#AppKind: FDS
D:\lvworm\src\lvsource\graphobjs.cpp(56) : DAbort:
0x0070644A - LabVIEW GPIBCloseDevOrUnit + 197BA
0x007063EC - LabVIEW GPIBCloseDevOrUnit + 1975C
0x00706384 - LabVIEW GPIBCloseDevOrUnit + 196F4
0x007138B8 - LabVIEW GPIBCloseDevOrUnit + 26C28
0x009854F3 - LabVIEW TDStandardize + 18F93
0x0085D16A - LabVIEW IsDialogControlFromRef + 1A95A
0x0081ABCE - LabVIEW OMGetClassPropListIds + 3E95E
0x008561FA - LabVIEW IsDialogControlFromRef + 139EA
0x0081ABCE - LabVIEW OMGetClassPropListIds + 3
E95E
0x00855FAE - LabVIEW IsDialogControlFromRef + 1379E
0x0081ABCE - LabVIEW OMGetClassPropListIds + 3E95E
0x009DB2DE - LabVIEW TraceToolEnableLogging + 5A9E
0x00A95F4B - LabVIEW SetKeyboardHandlerProc + 827B
0x00A8E0AC - LabVIEW SetKeyboardHandlerProc + 3DC
0x00B84639 - LabVIEW WSendEvent + 229

Hi, I have tried to open with lv7.1. The result is the same error message, but the log file differs....
Regards
Tamas
Attachments:
_GA_calc_by_point_positions3_defect.vi ‏1117 KB

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

Has anyone seen this error "window.cpp line 11518"

I have this error in my application and I am not printing or using an event structure. Apparently this error code has been found with printing front panels or using an event structure. I am using a case structure and all other cases are working properly. Once I get to this case labview displays this error and crashes. I deleted the case and the case structure and rebuilt it but I am still seeing the same problem. In this case there are two subvi's when the second subvi is executed this error is present when the second subvi is in highlighted execution the error is not present. If anyone has any suggestions please let me know. Thanks.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

After troubleshooting this problem more, I found that in the second subvi under vi properties, show front panel and close after if originally closed were not checked. Once checking both of these options the error did not occur anymore. Also this error was not present when the subvi was open in the background.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor

Error kernel.cpp line 144 on exiting an EXE

Similar Messages

Maybe you are looking for