A quick nugget today, since I've only got a few minutes between CLA Summit events. During my presentation this afternoon, I found that several of the CLAs in the room had never heard of the Heap Peek window. This is an internal LabVIEW feature that allows you to gain access to very detailed information having to do with how VIs are stored in memory. The most common use for the Heap Peak window is to identify and correct insane objects in your VIs.
To learn more about how to use the Heap Peek window, check out Bob Young's informative post here. One small correction to his information...if you are on Mac or Linux, you must use the INI token LVdebugKeys=True (note the capitalization). A little mini-nugget: capitalization does not matter for LabVIEW INI tokens on Windows, but it does on Mac and Linux.
The most common use for the Heap Peak window is to identify and correct insane objects in your VIs.
What can we do about the insane objects that operate our VIs?
Have you tried off loading them to a different customer support officer?
Happy to See "Insane Object" being caged into Nugget.
All LabVIEW user should be aware of this Heap Peek window (LV RnD Window). Once I spent my day on this to figure out issue during building Exe.
Thanks Darren's 🙂
This is an old thread, but...
I tried the directions to get into the Heap Peek, but I couldn't get it to work until I found an explanation at http://labviewwiki.org/Insane_Objects, which said to press CTRL+SHIFT+D+H all at once instead of "Press CTRL+SHFT+d, then press CTRL+SHFT+h" in the linked post.