12-20-2009 02:47 PM
Yes, it still does it for the shipping one, but rarely. It does it alot for my objec toriented code with many levels of abstraction. It is certainly possible I forgot to delete something somewhere, but when the program exits, it should take care of that if it's memory, I'm not sure what it does for memory mapped IO. Could be that, but that doesn't explain why it fails on the one they give out.
Also, no improvement since the new update to the drivers for NI-8451.
12-21-2009 09:52 AM
Hello blah32,
Please take a Spy capture again and set it to stop on your error. Specifically, go to Spy»Options and click on the tab Error Action. Configure your window to look like the following:
Please post this spy capture once you've got it. If this only happens occasionally in the shipping example, but very frequently in your code, it sounds like we again have left a connection open to your unit or perhaps you are opening and closing references inside of a loop. I look forward to this capture so that hopefully we can shed some light on what's happening here. Thanks and have a great day.