LabVIEW

Chriscort-

                 .cpp errors are internal crashes. If you post an example VI that can run on any computer and steps to reproduce the error then I can pass it off to our R&D team for further analysis. There are a couple of line 209 CARs (corrective action request) already in work but I would need to see an example of the error to see if this pertains to one of them or if this is a new case. None of the error codes centering around this have any promising leads so far so I don't have any positive news on a fix for you. Post it up and I'll see what I can find for you. Thanks!!

I've attached a minimal COM server (that starts a thread when events are requested) that shows the issue.  Steps to reproduce with LabVIEW 8.6 on Windows XP for x86 follow(stuff in parenthesis are comments):

(1) unzip HelloClass.zip to C:\ (4 files:  hello.vi, callback.vi, HelloClass.dll, Hello.tlb)
(2) C:\>regsvr32 helloclass.dll (should get "DLLRegisterServer in helloclass.dll suceeded." dialog)
(3) C:\>hello.vi (start LabVIEW)
(4) Ctrl+R (run the VI.  You should see "Command: test" in the String Indicator.  At this point the last call into the server is AddRef() but should be Release())
(5) Alt+F4 (close the VI)
(6) Alt+F4 (close LabVIEW)

You may need to perform steps 3-6 up to ~10 times, because at this point one of 3 behaviors randomly occurs:
(A)  Fatal Internal Error : "ThEvent.cpp", line 209
(B) Release() is finally called the same # of times as AddRef(), causing the destructor ~HelloClass to run (which kills the thread).  This should instead happen after step 4 (which it does if you remove the "Reg Event Callback" block)
(C) Release() is called several times, but not enough to decrement the reference count to 0

Behavior A doesn't occur if the server doesn't start the thread.  In source.zip, I've also attached the server's source code for your R&D team along with dbgMon, which is useful for looking at the _RPTF debug output.  Thanks much for your patience and for looking at this.

chriscortopassi-

                     I have passed off all you information to our R&D team and they are working on it at the moment. Unfortunately .cpp (internal) errors normally just have to be fixed and then rolled into the next version of LabVIEW because it is a low-level bug. If they find a work around though, I will let you know. Thanks for the feedback and helping LabVIEW evolve a little more. Cheers!!

Hi,

It's been over a month and I'd much appreciate it if NI could please just let me know if

(a) NI could reproduce

(b) whether NI plans to change something in a future LabVIEW release, or whether it's something I need to change

Thanks and happy holidays!

Hello!

This was reported to R&D (# 130282) for further investigation.  Additionally, I was able to reproduce this error on the first try.  I will make sure to update the CAR.

Any update on this bug?  I just saw it today using LabVIEW 2010 (10.0f2).

And yes, I realize this is a 4 year old thread..  The fact it still exists may indicate that it was never fixed.

I got line 236.