LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"Cannot find object in object heap" - LabVIEW crashes while opening project

For reference, I am running LabVIEW 2017 SP1 32-bit on a Windows 10 machine.

 

I have a certain project which I am unable to open due to this crash occurring every time. I do not know for sure at what point this became the case as I inherited all of the code I'm working with recently - this is my first time ever trying to open the project. I've done quite a bit of searching but can't find any information on the particular error I'm seeing. What I think I have identified is that this is being caused by a particular VI in a packed library (PPL) that's included in the project. Here's the log output, with the path to the VI modified for privacy:

 

<DEBUG_OUTPUT>
1/21/2019 12:15:05.651 PM
DAbort 0x07F89DC9: cannot find object in object heap, object dpid=9 uid=0
e:\builds\penguin\labview\branches\2017\dev\source\objheap\objheap.cpp(577) : DAbort 0x07F89DC9: cannot find object in object heap, object dpid=9 uid=0
minidump id: 41d4e898-70c5-4677-a76c-42ceadd4da16
$Id: //labview/branches/2017/dev/source/objheap/objheap.cpp#2 $

</DEBUG_OUTPUT>
0x00642589 - LabVIEW <unknown> + 0
0x0FE2FAC9 - mgcore_SH_17_0 <unknown> + 0
0x0FE3060C - mgcore_SH_17_0 <unknown> + 0
0x010978CA - LabVIEW <unknown> + 0
0x011223E0 - LabVIEW <unknown> + 0
0x01124F1E - LabVIEW <unknown> + 0
0x00D2951E - LabVIEW <unknown> + 0
0x00D2909E - LabVIEW <unknown> + 0
0x011249EE - LabVIEW <unknown> + 0
0x01124B0E - LabVIEW <unknown> + 0
0x00E08A53 - LabVIEW <unknown> + 0
0x00D2909E - LabVIEW <unknown> + 0
0x011249EE - LabVIEW <unknown> + 0
0x01123A93 - LabVIEW <unknown> + 0
0x0112692E - LabVIEW <unknown> + 0
0x01125E91 - LabVIEW <unknown> + 0
0x01119F93 - LabVIEW <unknown> + 0
0x01119267 - LabVIEW <unknown> + 0
0x0111DDEE - LabVIEW <unknown> + 0
0x00F8858D - LabVIEW <unknown> + 0
0x00F886A0 - LabVIEW <unknown> + 0
0x00FB9DC9 - LabVIEW <unknown> + 0
0x01108CAF - LabVIEW <unknown> + 0
0x005E31FD - LabVIEW <unknown> + 0
0x005E197F - LabVIEW <unknown> + 0
0x005E3ACC - LabVIEW <unknown> + 0
0x005E4013 - LabVIEW <unknown> + 0
0x005E1D6E - LabVIEW <unknown> + 0
0x005E1D1F - LabVIEW <unknown> + 0
0x00B8D087 - LabVIEW <unknown> + 0
0x00B94F75 - LabVIEW <unknown> + 0
0x00B8E3F7 - LabVIEW <unknown> + 0
0x00B8E446 - LabVIEW <unknown> + 0
0x00F952B0 - LabVIEW <unknown> + 0
0x00FC8C5D - LabVIEW <unknown> + 0
0x00FC4B07 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x002F0000 ***
Loading VI Heap, HeapClass "BDHP", C:\Path_to_PPL\ProblemPPL.lvlibp\Path\Within\PPL\ProblemVI.vi
*** End Dump ***

 

I have verified that the path to the VI is correct and the VI is not broken. I tried mass-compiling the PPL source and rebuilding the PPL but this didn't help. I'm really not sure what else to try and am having a lot of trouble finding any info on this specific type of crash. I'm not sure how to even figure out what object in the VI might be causing the problem. If anyone has insight on this, it would be most appreciated. Thanks!

0 Kudos
Message 1 of 3
(2,503 Views)

You MAY be able to edit the .lvproj file in a text editor and remove the offending PPL, then see if it opens. If it does, try re-adding the PPL back in and seeing if the problem comes back.

0 Kudos
Message 2 of 3
(2,498 Views)

Thanks for the response. While this hasn't quite answered the source of the issue and I wasn't actually able to do quite what you suggested, your idea gave me another idea to open the project which worked. It turned out that the offending PPL was a dependency of a VI in an auto-populating folder within the project, but it wasn't actually being called at all. Because of this it wasn't found explicitly called out in the .lvproj file. I was able to open the project by temporarily moving the offending PPL, so the project wasn't able to load it. I then removed the auto-populating folder in the project, and the issue is resolved since it's no longer looking for the problematic PPL. I'd still be curious to know why the crash was ultimately happening, but I am satisfied with the ability to continue working. Thanks! 🙂

0 Kudos
Message 3 of 3
(2,468 Views)