Crashing occurs when closing and opening a VI

[Eric1977]

All,

I am working on a project that generates crash reports. I've looked and looked and I can't seem to find where the possibility of the crash is occurring. It only does this if I close the VI and reopen it. My guess is that I am not closing something gracefully but I can't identify it.

I am hoping someone can take a look and let me know where the crashing might be occuring.

[billko]

---

@Eric1977 wrote:

All,

I am working on a project that generates crash reports. I've looked and looked and I can't seem to find where the possibility of the crash is occurring. It only does this if I close the VI and reopen it. My guess is that I am not closing something gracefully but I can't identify it.

I am hoping someone can take a look and let me know where the crashing might be occuring.

---

Isn't it ironic that it is the crash report generator that is crashing?  I'm looking at it now.  😄

[billko]

Which VI was that?  (Also, some files seem to be missing.)

[Eric1977]

Should me Main.vi.

Which files seem to me missing?

[billko]

[rolfk]

---

@Eric1977 wrote:

All,

I am working on a project that generates crash reports. I've looked and looked and I can't seem to find where the possibility of the crash is occurring. It only does this if I close the VI and reopen it. My guess is that I am not closing something gracefully but I can't identify it.

---

Does it crash right when reopening the VI or only after you start it again?

[Eric1977]

Bill - here are the missing control and clusters.

[Eric1977]

It seems to happen right as it reopens. You'll get a few successful runs with the VI but takes 2-3 times before it fails and crashes.

[Eric1977]

rolfk,

Here's the crash report which looks like memory addressing?

[billko]

---

@Eric1977 wrote:

rolfk,

Here's the crash report which looks like memory addressing?

---

It's relatively difficult for LabVIEW to achieve a memory access violation because it is pretty good at keeping track of its resources.  This is usually caused by a dll causing an exception that makes LV crash.  Possibly .NET related?