03-08-2010 06:15 PM
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.
03-08-2010 06:57 PM
Darren wrote: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?
03-08-2010 07:42 PM
Darin.K wrote:
Darren wrote: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?
06-02-2010 02:14 AM
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 🙂
Regard
Hemant
02-10-2011 10:32 AM
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.
02-10-2011 10:49 AM
csalwen,
That link you posted has no information on the page.
02-10-2011 10:52 AM
Sorry, it got a comma into the link. It should be
05-18-2023 01:12 PM - edited 05-18-2023 01:13 PM
After I add this LVdebugKey, NXG button does not display correctly. It often remain in the OffHover color (white by default). Doesn't change color when hover or leave.
Take me a while to trace this down to the debug key.
Post it here to remind myself and anyone run into the same problem.
LabVIEW 2018 SP1 64bit on Windows 10 Pro.