@Relec wrote:
Fun Times.
I just did the exact same thing you did. Using an sbRIO 9637. So much time wasted because I assumed it was something I had coded that was causing the problem.
Unfortunately I don't have the option of upgrading to LabVIEW 2019. Using 2018 SP1 at the moment.
It appears that I can run for about 20 hours before I start running out of memory. I might try to put an auto-reboot in the code. Which isn't much of a solution if you expect your system to collect data and run continuously for years.
Relec
I also have a project that crashes due to know memory after about a day of running on my myRIO. The code is also deployed on a sbRIO in the field and it doesn't experience the issue. The only difference is that the code in the field always has the connection to a message broker established and on the myRIO, which I use for testing purposes, doesn't have the message broker connection because I don't leave that running 24/7. The application will automatically try to re-establish the connection. That is the only difference in the execution path between the deployed system and my test bed. Since the deployed system isn't exhibiting this issue I haven't fully investigated the cause. I have tested out the messaging libraries for issues but this was done on a PC. This just shows that it is not a fundamental issue with the library itself.
Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
