LabVIEW
Error #3 memory.cpp line 945 (LV 6.1)?
memory.cpp errors are rather nasty in the sense that they are in a very low level part of LabVIEW. Bascially memory.cpp provides all memory management fucntions to about anything in LabVIEW and an error here means that one of the memory management functions either had a problem to satisfy a memory allocation request or most likely was passed a parameter it could not link to a previously allocated memory block.
@JBeltran wrote:I was wondering if anyone knew exactly what this error was for. I have found a couple errors inregards to the memory.cpp for lines 563 and 593 but nothing for line 945. The version is LabView 6.1. This error just started appearing yesterday after several months of error free use. It is for a data analysis program that has a primary function of loading in several megabytes of text delimited data from a server drive file and then plots it. The program crashes several minutes into the data load phase. I have tried to track down what may be causing this but I have been unsuccessful thus far. Any help would be apperciated.
Especially the later error is rather bad in the sense that it is just an indication that something has gone wrong somewhere in LabVIEW by calling a memory manager function with an invalid argument but it gives no further information as from which part this invalid parameter was passed. A stack trace would be rather helpful here and I think newer LabVIEW versions will create such a stack trace together with other information in your user directory to be sent to NI if you agree to the error dialog on startup. Problem is that this error log file seems to sometimes not be created at all on certain machines I have LabVIEW applications running at some customer site.
Older LabVIEW versions could also be persuaded to create some sort of error log file on assertions by adding some debugging=True to your labview.ini file after which a dprintf.txt file was created in your LabVIEW directory, but this functionality and ini file key have changed regularly and are not really documented at all.
The information in such an error log is still highly difficult to interprete for someone outside of the LabVIEW developer group but it can give you a few more hints and should help NI support to facilitate more specific information as to the possible culprit of the problem (although they are usually quite hesitant to give that specific information).
Rolf Kalbermatter
