I've been developing some code on a cRIO 9054, using the simple state machine and queued message handler architectures. A couple weeks ago we were running our code with no issues. Since then, we have left the cRIO connected to power but stopped running any code (that is, we put the cRIO in a safe state, then click "abort" red button on the target's top-level VI, since the front panel is empty).
Today, I went to run it again, but I got a mysterious error. The deployment status window doesn't list anything out of the ordinary except at the very end, where it says that the deployment has completed with errors (but no other details). After this, the VI is not running. The window also usually says that we still have around 72% of the total memory free, but this time it says no memory information available.
However, I found out (by right-clicking the target in the project explorer and going to Utilities > Target Information) that there is zero available memory out of the ~1.9 GB. This has actually happened before, and I got around it by restarting the device with MAX.
However, MAX isn't picking the cRIO up on the network anymore (it does detect a 2nd identical cRIO we have though), and Utilities > Restart in the project explorer gives me a dialog box saying that "An error occurred while attempting to reboot the target". We also can't access the room that the cRIO is in for another few weeks. But this might a separate issue altogether.
What I'd like to know right now is, is there a reason that the memory is filling up, even when we weren't operating the device at all the past couple weeks? Could it be that when we make a change to a VI and deploy it to the target, it's not clearing the old files from memory? I would like to prevent this from happening in the future.
