Heap Corruption Detected in Labview.exe

[George2]

Upon closing LabView 8.5, I get the following error message: 
Microsoft VC++ Debug Library
Heap Corruption Detected in Labview.exe
after 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,

The error message appears in the popup "Microsoft VC++ Debug Library" because you probably have Just-In-Time (JIT) debugging enabled in Visual Studio.  Please follow the linked instructions to disable debugging so that we can see where the crash occurs.  Once that's complete and you obtain theLabVIEW crash log, we can continue attacking the issue.  Goodnight!

[George2]

Hi Peter,

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

George2 

[Pakman]

Hi George2,

The JIT debugging option is independent of your DLLs. You should be able to launch Visual Studio, uncheck the option, and then run your application.  Then, the next time it crashes, Visual Studio will catch the error.

[George2]

Hi Peter,

We were able to track this problem to a bug in the 3rd party software.   Its now resolved. 

Thanks for your help!

George2 

[Pakman]

Great!  Thanks for letting me know.  Enjoy your night!