@Meanjean2119 wrote:
Makes it difficult to troubleshoot my application. Anyone else having this problem? I'm running LabView2024.
When running my application I want to see what variables are changing in a subVI, in a subVI, in a subVI...
Everything runs fine when in the primary VI. But once there are to many VIs open, I'll lose the "probe watch window" and sometimes the VI I'm probing will hang and I can't even stop it. I have to kill the whole application.
Are there a limit to how many windows I can open? There never seems to be any memory or CPU issues.
Thanks for any help.
I would look for unexpected breakpoints! There is a Breakpoint Manager as well as the Probe Watch Window available for advanced debugging. My magic 8-Ball says that you might have accidentally hit a Breakpoint you wished you had not saved.
Especially look for custom probes with a "Break---If" (like a VISA Break if Session is invalid probe) I can't imagine how ANY regression test set could cover a requirement like : "The Probe Watch Window SHALL NOT close when encountering a conditional breakpoint in a custom probe while the condition is TRUE."
Heck, NI would never get the bug report from anyone who accidentally wrote a bug and unexpectedly found that feature while debugging their own problem!
Aesop fable time.
The Jovian Bomb:
Once there was a cosmic ray that struck a DNA molecule of an animal on a moon of the planet Jupiter. Nobody on Earth noticed. The Jovians evolved. Nobody on earth noticed because they had to pay attention to their own business. One day , an Earthman made a mistake. While trying to fix his mistake he used a tool. The tool broke but he fixed the mistake anyway. The Eathman was relieved. The Jovian laughed and said, "That is how we can beat the Earthmen! Let's build tools for them that only break if they use them when they have first F'd up!"
"Should be" isn't "Is" -Jay
