Greetings List Contributors,
I've also had some difficulties with 8.5.1 RT (running on the now-discontinued PXI-8187RT controller). My upgraded application runs okay for about 5-10 minutes, then I lose the connection to the RT target. Based on the feedback from the RT System Manager, it appers there is some type of memory leak problem, as the memory usage increases steadily until the connection is lost. at this point, the RT system appears to have locked-up, as the RT video output stops updating as expected. I've tried profiling the VIs to see if one of them is steadily increasing it's memory footprint, but so far, I haven't been able to see anything odd (at the VI level, at least).
The application has been working fine under 8.5 on a newer PXI-8106 controller installed at a customer's site, but I wanted to check it out on the lab test system (the PXI-8187) before upgrading the customer's system to 8.5.1. (My reason for wanting to upgrade is related to a problem with shared variable bindings in built applications in 8.5. The app works great in the LabVIEW environment, but a bug in the run-time causes some of the shared variable bindings to 'miss' at times...)
So far, my inclination is to stay put at 8.5. I'm not ruling out that I'm creating a memory leak on my end by doing something careless like continually opening a reference in a loop and never closing it. However, I've looked for this sort of thing and can't find any problems. (I did encounter a problem with reading shared variables in a loop that caused a similar memory leak, way back in LV 8.2. It seemed to happen only in reference to a very large string -- specifically, a flattened JPEG image. Once I converted that particular shared variable read operation for use with the datasockets API, I was able to open the reference outside the loop, and read it explicitly inside the loop using the single, open DS reference. That solved that particular problem. The behavior here looks suspiciously the similar... but I don't have any particularly large strings or arrays mapped to a shared variable in this application. A couple of dozen small shared variables, but nothing too big.)
There is one consideration -- the Vision version I'm running is still 8.5. (There was no Vision 8.5.1 update included in our last Developer Suite quarterly installment.) Perhaps LV 8.5.1 RT requires Vision 8.5.1..? Just a thought.
Anyway, I've been looking at this for a couple of days, off and on, as time permits. My own testing has not been completely exhaustive yet. But I guess the question is whether others are experiencing similar 'behavior enhancements' with 8.5.1 RT, and in particular, in the context of vision-based applications.
-- D.
LabVIEW user groep 
