Labview 2012 Runtime Application Crash: Access Violation Error

[Michael.Proctor]

hi All,

my rather large app that I been develping over teh last few years has recently been crashing.

I do not know if it is since I began compiling it in LV2012 SP1 that the problem occurred or I have some programming error

that I cannot track down.

It use to run with uptimes over months, even with some memory leaks.

If I monitor using Task Manager there is no decernable increase in memory usage.

It crashes on two different systems - both running Windows XP.

The developer version running in LabVIEW 2012 f5 ( Windows XP ) does not crash. Only the runtime version crashes.

It also crashes either if the program sits idle for a few days - 5 or so ( memeory footprint stable ), or if it is used extensively to actively gather and control several instruements ( memory increase matches data size increase )

It does call several external API via ActiveX to spawn off processes, however from the lvlog.txt it seems the crashing is a simple open file that uses the NI supplied String to Config.vi.

I have double/triple check my code and I close any refernces open by the calling vi.

I am sure how to read teh mini-dump files so if someone can look at these it would be apreciated

thanks

Michael

Here are two crash logs:

[Spicy_Mystery]

Hi Michael,

It's tough to tell what's going on, especially since it seems like you've really covered your bases!  I'm curious about the fact that you don't see the crashes in LabVIEW (LV), just in the Run-Time Engine (RTE).  Have you ever tried running it in LV for an extended period of time?

Also, do you have any loops in your program?  Perhaps shrinking any waits that might be present and allowing your program to run faster would decrease the amount of time to see these errors from days to shorter.  

In the future, when you get a dump file, submit it to our R&D department.  It then pops up on a website that allows me to read them.  I can also use win debug but that will take me a bit, so I'll have to get back to you on that.  

Also, if you could take a picture of the error, that would help as well.