Heap Corruption Detected in Labview.exe

[George2]

Upon closing LabView 8.5, I get the following error message:  Microsoft VC++ Debug LibraryHeap Corruption Detected in Labview.exeafter Normal block #47 at 0x05CD21A0 CRT detected that the application wrote to memory after the end of the heap buffer.  When I try to follow the option to debug the application, I get the message that there are no debuggable libraries.Is this an error with LabView.exe or with one of my vi's?

[Wiebe@CARYA]

Unless you use heap or memory allocating API's it is a LabVIEW.exe message.

Regards,

Wiebe.

[Pakman]

Do you receive that error message every time you close LabVIEW or only under certain conditions?

[George2]

Peter, I get this error message when closing LabView 8.5 after running a specific application consisting of many vi's.  I've run the same application under LabView 8.2 with no problems.  What seems odd to me is that the error message appears in a popup titled "Microsoft VC++ Debug Library", as opposed to a native LabView error dialog.  Any suggestions as to how to chase this down?Thanks,George2

[Pakman]

Hi George2,&nbsp;The error message appears in the popup &quot;Microsoft VC++ Debug Library&quot; because you probably have <a href="http://msdn.microsoft.com/en-us/library/k8kf6y2a.aspx" target="_blank">Just-In-Time</a> (JIT) debugging enabled in Visual Studio.&nbsp; Please follow the linked instructions to disable debugging so that we can see where the crash occurs.&nbsp; Once that's complete and you obtain theLabVIEW crash log, we can continue attacking the issue.&nbsp; Goodnight!

[George2]

Hi Peter,&nbsp;Thanks.&nbsp; This application uses third-party software - specifically .dll's - that were provided without source code.&nbsp; I'll have to get the source from the contractor in order to rebuild without JIT.&nbsp; Will do and will be in touch shortly.&nbsp;George2&nbsp;