Heap Peek is Driving Me Insane!

[curiouspuya]

Hi all,

 

This week I am pulling my hair out trying to fix a big project of mine that produces an executable with no errors which then does not run (crashes).  Upon mass compiling the project (waiting 4hrs) I found a bunch of insane objects in various VIs.  An example of one is:

 

Insane object at FPHP+2C30A9C0, UID 8, in "VdMiyachiLW25AWeldingLaser.lvclass:SendCommand.vi": {tdname } (0x4000): Numeric (DDO )
insanities in FPHP of C:Program Files (x86)National InstrumentsLabVIEW 2012instr.lib_InstrumentDriversVdInstrumentsVdWeldingLaserVdMiyachiLW25AWeldingLaser_classSendCommand.vi
 

Note the number of the object in bold above.  I then went an started Heap Peek (ctr+shift+d+h) in an attempt to find and clear the insane objects (for more info on heap peek see: http://labviewwiki.org/Insane_object).

 

The trouble is that I cannot find the offending objects as per their numbers.  They simply do not appear.  So short of deleting all possible controls and indicators and replacing thme I have not find an easier way to sort out my problem.

 

 

Does anyone have experience with Heap Peek?  Have you had this problem with it too?  Am I missing something here?

 

Thanks for any help! 

 

 

Puya

[Mr Mike]

Click the uo button (I think it means "UID ordered") to sort the objects by UID.  The UID is the first number in the rows (see attachment)

That should help you find it.  I don't know why it's not not showing up in order in the memory-ordered list.

[curiouspuya]

Thanks Mr Mike,

 

I have more problems here than I thought!  Now I am finding that I get insane objects in VI's that do not appear in the list.  For example this line:

 

Insane object at FPHP+33819BE8, UID 43, in "ETA4_CalibrateTube2CameraOffset.vi": {tdname } (0x4000): Type Definition (DDO )
 

The above VI should appear on the list on the left in the FPHP group but it is not even listed!!!

 

 

Any ideas?

 

Thanks

 

Puya

 

 

-----------------------------------------------------------------------

 

 

It works thanks Mike!!  I just tried your UID suggestion and was able to find the item that way.  I think the wiki page should be updated with this method!

 

 

 

 

 

As for my other problem of not finding the VI in the list, it is because I was opening Heap Peek just from the project window.  I found that I actually have to open the offending VI first and then open Heap Peek.  This changes the list that appears.

 

Thanks again for your help.

 

Puya

Edited January 10, 2013 by curiouspuya

[Mr Mike]

My guess is that you're looking in the wrong context.  If you scroll to the top of the heap list (the one you show in the image above), you'll see that they're broken up into contexts.  In general, there are two contexts you will encounter: the Main Application Instance and Project contexts.  The Main Application Instance contains VIs opened without a project.  Project contexts have the VIs in a project that are on a specific device (i.e. My Computer or an RT Target).  There are tons of other contexts that handle internal stuff, but your VI shouldn't be in those.  Check all the contexts that sound relevant to your VI.  If that doesn't work, I'll forward this to someone who knows better than I.  I just use Heap Peak -- I've never seen how it works on the inside.

[curiouspuya]

I also thought it might be a context thing but i painstakingly scrolled through the entire list and never found the vi (unfortunately they didnt provide a "Find" function   ) .  What I found instead is that you find the right context by opening the VI thats giving you trouble before opening Heap Peek.

 

By the way I managed to fix the insane objects in the end and my executable no longer crashes!  Happy Ending!

 

thanks again for your help Mike.

 

P