Error on exit DAQ Program: MechFactoryCWrap.cpp

[Andrew Munro]

On exit of the program, I see the dialog (jpeg attached). The associated error log contains data as follows:

####
#Date: Wed, Nov 15, 2006 5:54:58 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 7.1
#AppKind: FDS

D:\lvmerc\src\source\execsupp\MechFactoryCWrap.cpp(649) : DWarn: Max space cannot be zero; changing to -1 (unbounded)
$Id: //labview/branches/Mercury/dev/source/execsupp/MechFactoryCWrap.cpp#3 $
0x00A35B37 - LabVIEW + 0
0x00A346F5 - LabVIEW + 0
0x00A3688C - LabVIEW + 0
0x00A349A3 - LabVIEW + 0
0x00A3565C - LabVIEW + 0
0x09A2B69D - + 0
0x014EA940 - + 0
0x00A09110 - LabVIEW + 0
0x8B535CEC - + 0

Note that my program accesses two spectrometers, each using a separate DAQ, and uses queue structures to store and display the data.

[Andy F.]

Hey Andrew. 

Was this error message after a crash or just starting LabVIEW?  Since it is a DWarn type I would not be surprised if there were no crash along with it.  Does your program use any timed loops?  In any case this isn't something that should be troublesome unless you start noticing it a lot.  If you do notice it a lot go ahead and submit this when it prompts you to investigate the internal error.  This particular error should be fixed in LabVIEW 8 and higher in any case.  Please let me know if you have any questions.

Thanks!
Andy F.

[Andrew Munro]

Thank you for taking the time to answer, Andy!

The dialog appears when I close my LabVIEW application; it may be a pop-under error window, however I don't notice it when the program is running so I'm led to believe it appears on close.

The main code uses several timed loops running in parallel to divide the tasks (e.g. DAQ, UI/display, Serial IO), hence the use of the queues. 

Unfortunately I'm unable to submit the error because the target PC is not on the network.  I selected the "do not prompt.." option/checkbox and haven't seen the error since.

Cheers,

Andrew

[Andy F.]

Andrew,

It could actually be during execution that the error occurs, but you not know it until LabVIEW is closed and re-opened.  You can check to see if there are additional logfiles in the "\My Documents\LabVIEW Data\lvfailurelog" folder, where My Documents is wherever that folder is located on your computer.  Normally these types of errors can be recovered from and that seems to be the case that you are seeing.  Please let me know if you have any additional questions.

Thanks!
Andy F.