Fatal build error DAbort 0x9B027400

[Mike Le]

Hey guys, running into an application error that crashes LabVIEW entirely.

 

The project file is about two years old and we've been doing builds on it a couple times every month with updates to the original application.

 

Recently, we were getting an error 1003 on build attempt, claiming one of the VIs was broken. Everything ran fine in Developer mode and the "broken" VI ran fine as well, no broken arrow. We did a mass compile, which didn't resolve the problem.

 

Finally, I took the "broken" VI and renamed it. Then I saved a copy of the renamed VI back to the original file location. The 1003 error during builds went away.

 

Instead, the build would progress maybe 1/6th of the way through the progress bar, then completely crash the LabVIEW developer environment.

 

Here's the error message we get from LabVIEW Crash Reporter:

 

DAbort 0x9b027400 in drawmgr.cpp.

Version: 12.0.1f4 (32-bit)

 

Any ideas? Attached is the error data.

Compile Error Report b73bd0d6-4f5d-400e-8b1a-071df67cf3c3.zip

[JackDunaway]

Does the offending VI contain a Diagram Disable structure?

 

While you're checking, do an object search on the entire hierarchy for Diagram Disable structures, and missing VIs in disabled cases. Likewise, search your project by right-clicking the root node and selecting "Find Missing Items"

[Gajic4x4]

This is cross posted on the NI forum.

 

Posted my solution there.

 

https://forums.ni.com/t5/LabVIEW/Fatal-Internal-Error-quot-drawmgr-cpp-quot-line-3793/m-p/2570253/highlight/false#M775082