Another LabVIEW Crash

[test_man]

After I clicked OK Following error occured.

I was closing my front panel when this errors occured.

Message Edited by Sheetal on 10-02-2006 05:00 PM

[altenbach]

You neet to attach your images. Currently, they point to your C drive, a location we cannot access.

[test_man]

Here they are

[altenbach]

Apparently, you are using LabVIEW 8.20. Time to update your posting signature. 😉

Anyway, I've never seen "ThEvent.cpp", Line 152. You should report this to National Instruments.

Is this a one-time occurence? Do you have a step-by-step procedure to generate this error?

[test_man]

It is one time occurence as far as I know. And just like many other crashes I have seen this is also not repeatable.

[NIJanell]

Hello Sheetal,

Upon reopening LabVIEW, did you receive a dialog box asking you to send a error/crash log file to National Instruments?  From what I can tell, this is a new issue, so in order to fix it, we will need to reproduce it and get that log file.  In your previous messages, you said that you cannot replicate it - has anything changed?  Were you doing something different during that run compared to others?

Thanks,

Janell Rodriguez | Applications Engineer | National Instruments

[test_man]

Yes. It did ask me to investigate. I have attached that file. I think some of the crashes I have seen has something to do with undo/redo which I do a lot.

[Sige]

I also had similar crash.

Message Edited by Sige on 10-04-2006 03:17 PM

[ronbrown]

I received this error today as well in LabVIEW 8.20. 

LabVIEW becomes completely unresponsive if I do not quickly dismiss the error's dialog box.  I do not recieve the dialog asking me to report to National Instruments, although I may have disabled that option.  It seems to be rather reproduceable.  My app is rather complicated, so I can't attach it here, but I'll make an attempt at describing what I'm doing when it crashes.  It seems to happen while handling an event signalled by my ActiveX callback VIs.  Through a COM interface, we fire an event.  I have a callback VI setting a boolean's Value (signaling) to True.  Inside the main app, I have an event handler loop waiting for that value to be set to true, and when it is, I do my thing.  Seems to work for a few seconds, then BAM!  Error message pops up.

It seems that if I try and slow that event handler loop down, by throwing a 60 ms Wait in the surrounding While Loop, it does not happen.

In any case, I hope that helps.