Labview "Fatal Internal Error "memory.cpp" line 1038

[jcao]

Hi,

This is an example file provided by NI and can be found in Labview 8.2\examples\instr\niHSDIO: Dynamic Generation.lib. Inside this library, there is a file called "Dynamic Generation.vi". If I copied "Dynamic Generation.vi" to other place, the labview will crash. Error message:

"Fatal Internal Error. "memory.cpp". Line 1038. Labview version 7.1.1. You will lose any unused work, please contact NI, etc, etc"

In the mean time, the Windows freeze. Mouse right click no response. No status bar at the bottom of the screen. The whole desktop is blank. All icons on the desktop disappeared. I have to log-off and re-login to re-active everything.

I also tried to copy other VI's in other library files. Same thing happened.

Thanks,

Jing

[jcao]

Anybody can help me on this issue?

Thanks!

Jing

[Nadim R]

Hi Jing,

Are you getting the memory cpp error when you try to run the dynamic generation vi in LabVIEW 7.1.1 or LabVIEW 8.2? Furthermore, what do you mean by copy the vi to the other place? 

Once we know what version of LabVIEW you are trying to run the VI in, I will check upon some databases and see if there are any current workarounds or if the error has been fixed.

Regards,

Nadim
Applications Engineering
National Instruments

[jcao]

I was using Labview 8.2.1 when I had this crash, though I have Labview 7 installed in the same computer.

When I "copy the file to some other place", I mean: Click the *.vi file, ctrl-c and ctrl-v to some other directory.

Thanks,

Jing

[Nadim R]

Hi Jing,


Thank you for your reply.  I found the .lib file, opened up the library in LabVIEW 8.2.1 and then copied over the specific vi (dynamic generation) to a new location.  I then opened it up and everything worked fine.   This leads me to believe that when you double click the VI, you are actually trying to open up the VI in LabVIEW 7, since you are getting the memory error with LabVIEW 7.  Note that if you open up the .lib file  from Windows, it may open up all of the files in that library, which may cause a memory problem that you are facing.  A better way to open up the library is to first open up LabVIEW and then open up the library and select the specific VI.

I hope this helps,

Regards,

Nadim
Applications Engineering
National Instruments

[linlan]

Nadim

I have the same peoblem "Fatal Internal Error "memory.cpp", line 1038" with LabView 7.1 once a while. The VI writes data into a excel file every minute normally but it suspended last night as the excel could not be closed. It happened rarely and it ran well once I restarted the computer. Is it related to LV 7.1? Here is the LabVIEW Data\lvfailurelog\lvlog07-11-08-09-51-29.txt.

Thanks. Lin Lan

####
#Date: Thu, Jul 10, 2008 2:58:28 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.1
#AppKind: FDS

D:\lvmerc\src\source\data\data.cpp(119) : DWarn: fpdco dataptr dsoffset=0
$Id: //labview/branches/Mercury/dev/source/data/data.cpp#5 $
0x004B99A3 - LabVIEW <unknown> + 0
0x009E364E - LabVIEW <unknown> + 0
0x00768F8C - LabVIEW <unknown> + 0
0x009E46BE - LabVIEW <unknown> + 0
0x007695A7 - LabVIEW <unknown> + 0
0x009E46BE - LabVIEW <unknown> + 0
0x00769139 - LabVIEW <unknown> + 0
0x009E46BE - LabVIEW <unknown> + 0
0x00768F9A - LabVIEW <unknown> + 0
0x009E46BE - LabVIEW <unknown> + 0
0x00768D4E - LabVIEW <unknown> + 0
0x009E46BE - LabVIEW <unknown> + 0
0x0061B3AE - LabVIEW <unknown> + 0
0x00A03132 - LabVIEW <unknown> + 0
0x009FACE5 - LabVIEW <unknown> + 0

D:\lvmerc\src\source\data\data.cpp(119) : DWarn: fpdco dataptr dsoffset=0
$Id: //labview/branches/Mercury/dev/source/data/data.cpp#5 $
0x004B99A3 - LabVIEW <unknown> + 0
0x009E364E - LabVIEW <unknown> + 0
0x00768F8C - LabVIEW <unknown> + 0
0x009E46BE - LabVIEW <unknown> + 0
0x00768D4E - LabVIEW <unknown> + 0
0x009E46BE - LabVIEW <unknown> + 0
0x0061B3AE - LabVIEW <unknown> + 0
0x00A03132 - LabVIEW <unknown> + 0
0x009FACE5 - LabVIEW <unknown> + 0
0x004B7F79 - LabVIEW <unknown> + 0
0x004B7E3C - LabVIEW <unknown> + 0
0x004B7CF9 - LabVIEW <unknown> + 0
0x004B520D - LabVIEW <unknown> + 0
0x004B347E - LabVIEW <unknown> + 0
0x7E418724 - USER32 <unknown> + 0

[Chris_VH]

Lin Lan,

Are you using the same example as the original poster, or are you just experiencing the same error? 

Also, are you trying to move libraries or use them, or are you just trying to run a VI?

[linlan]

Chris

This is the same error in my VIs, nothing to do with the original poster.

I am running VIs in LabView 7.1.

Thanks.

Lin Lan

[Chris_VH]

Lin Lan,

The error you experienced is a warning that occurred during the last time you were using LabVIEW. By default LabVIEW does not show a dialog at the time of the warning since it is not critical to execution. However, it is hard to identify the cause of the DWarn (for investigation purposes) without knowing when it occurred. By adding the following line to your LabVIEW.ini file you will see a dialog immediately when the error occurs, which will help you (and NI) identify the cause.

DWarnDialog = TRUE

If you are running critical code on your machine, you may not want to add this token since it will show a dialog and halt execution of your program when the DWarn error occurs.

If you want to disable the reporting of the warning all together then remove DWarnDialog=True from the LabVIEW.ini file and add the following line instead.
DebugLogSkipList = {filename.cpp}({linenumber})

[1000a]

Hello,

I am writing here because i have the same error message that  Lin Lan and Jing.

For me it happends when I tried to copy files from a library to another folder. These libraries were developped using the version 7.1 and now I am using 8.6. I have opened them and saved the automatical changes done by Labview to adapt them from a version to another.

Now I am trying to develop a new project in which i need to use and modify some of this files, so what i did is to add the libraries to the proyect, to take the main vi (which was also in one of these libraries), and made all the necessary changes for the project to the files directly in the library. I was not very sure whether this is a good practise or not and I asked in the forum. Someone adviced me to extract the files from the libraries, save them in the memory of the PC and add them to the project. However, when I try to copy the files to a folder, I get that mistake (and even internet explorer is closed)

My PC has Labview 7.1 and 8.6 installed. Maybe I wouldn't mind to remove the old version of Labview, only if that stops the problem (because if i want to install it again, previously i have to remove the newest version, instal 7.1 and then again 8.6....)

Thank you very much!!