BobHamburger Posted July 9, 2008 Report Share Posted July 9, 2008 I've decided to start my own LabVIEW blog, to share random observations and debugs which I believe could be helpful to my fellow LabVIEW jockeys. Here's my very first entry! Feel free to leave feedback, comments, critique, etc. I hope that my insights can live up to the high standards of this community. Quote Link to comment
mje Posted July 9, 2008 Report Share Posted July 9, 2008 Hehe, I've been burned by stuff like that. In general, one shouldn't obtain a reference (to anything) inside a loop, especially if that reference isn't closed on the same iteration. Quote Link to comment
Yair Posted July 9, 2008 Report Share Posted July 9, 2008 Congratulations on the new blog. I assume that this happens because RT doesn't do some optimizations which LabVIEW on Windows does in order to keep the RT run-time smaller and lighter. Quote Link to comment
LAVA 1.0 Content Posted July 9, 2008 Report Share Posted July 9, 2008 QUOTE (Yair @ Jul 8 2008, 07:43 PM) I assume that this happens because RT .... Sorry to disappoint you, this happens on any given platform. Every iteration a new queue reference is created, this is 4 bytes of data. By creating a loop at 5 ms I could easily see the memory usage rise of LabVIEW. Ton Quote Link to comment
Yair Posted July 9, 2008 Report Share Posted July 9, 2008 I was thinking of adding that I'm actually a bit surprised and that I would actually expect it to behave the same way on both platforms (either to optimize or to perform the code literally), but I decided against it, since I figured that Bob probably had a reason to say that it worked fine. I guess I should have tested it myself. Quote Link to comment
BobHamburger Posted July 9, 2008 Author Report Share Posted July 9, 2008 QUOTE (Yair @ Jul 8 2008, 02:47 PM) I was thinking of adding that I'm actually a bit surprised and that I would actually expect it to behave the same way on both platforms (either to optimize or to perform the code literally), but I decided against it, since I figured that Bob probably had a reason to say that it worked fine. I guess I should have tested it myself. Well, to the extent that I tested it under Windows, it appeared to work fine. The RT systems were left running overnight and over weekends, and that's when the memory leaks would eventually cause things to crash. We never did long-term tests under Windows. Quote Link to comment
Jim Kring Posted July 9, 2008 Report Share Posted July 9, 2008 Bob, Welcome to the club. I've posted a short welcome announcement here. Cheers, -Jim Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.