Crash during deploy (DWarn 0xB8CFE56F)
dbendele opened this issue · comments
When trying to test DCAF 1.2.3, observed LV 2017 crash during deploy of cRIO Main.vi from the RT Temperature Controller example.
Steps to reproduce from clean image:
install LabVIEW 2017 and LabVIEW Real Time
install device drivers
install NI-RIO 17.0
Install DCAF Core (1.2.2 as of 20171023) from LabVIEW Tools Network
Update with DCAF Core 1.2.3 vipc (https://nio365.sharepoint.com/sites/DCAF47/Shared%20Documents/General/DCAF_1.2.3.vipc)
Configure the simulated configuration for your system
Deploy cRIO Main VI
crash was observed during deployment
664e350a-ec19-41e6-a7be-b9dd92d36162.zip
from that attached report:
<DEBUG_OUTPUT>
10/23/2017 1:42:40.098 PM
DWarn 0xB8CFE56F: Expecting first element of FPDCO's (0x2b8e6140) termlist to be vacant: element 0x2b7f09a0
e:\builds\penguin\labview\branches\2017\dev\source\panel\loaddata.cpp(2282) : DWarn 0xB8CFE56F: Expecting first element of FPDCO's (0x2b8e6140) termlist to be vacant: element 0x2b7f09a0
minidump id: 0b8f7607-f589-46a2-9383-44976988b8d3
</DEBUG_OUTPUT>
0x01662EB9 - LabVIEW + 0
0x644BFEB9 - mgcore_SH_17_0 + 0
0x644C09FC - mgcore_SH_17_0 + 0
0x02137F2A - LabVIEW + 0
0x01DAED84 - LabVIEW + 0
0x02138D59 - LabVIEW + 0
0x0200EEAB - LabVIEW + 0
0x0200EF54 - LabVIEW + 0
0x0200EEE5 - LabVIEW + 0
0x0213F3AC - LabVIEW + 0
0x0213E78E - LabVIEW + 0
0x0213DCB1 - LabVIEW + 0
0x02131CD3 - LabVIEW + 0
0x02130FA7 - LabVIEW + 0
0x02135BDE - LabVIEW + 0
0x01BA7A2E - LabVIEW + 0
0x01BA7C56 - LabVIEW + 0
0x01FAB718 - LabVIEW + 0
0x01FAC200 - LabVIEW + 0
0x01FAD26D - LabVIEW + 0
0x01FE088D - LabVIEW + 0
0x01FE9364 - LabVIEW + 0
0x01FD75B2 - LabVIEW + 0
0x01FD197B - LabVIEW + 0
0x02120E4B - LabVIEW + 0
0x01603C1D - LabVIEW + 0
0x0160238F - LabVIEW + 0
0x016044EC - LabVIEW + 0
0x01604A33 - LabVIEW + 0
0x0160277E - LabVIEW + 0
0x0160272F - LabVIEW + 0
0x01BA6867 - LabVIEW + 0
0x01BAE765 - LabVIEW + 0
0x01BA7BD7 - LabVIEW + 0
0x01BA7C56 - LabVIEW + 0
0x01FAB718 - LabVIEW + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x01310000 ***
Loading VI Heap, HeapClass "BDHP", C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\NI\DCAF\Engines\Standard Engine\Execution Engine\async executor\async worker process.vi
*** End Dump ***
Note, this issue has not been observed in other versions of LabVIEW.
It appears issue was introduced between packages/builds 2.4.0.2 and 2.4.0.5
we believe that we have worked around LV 2017 issue by making a select change to write syslog.vi in LabVIEW-DCAF/syslog repo