Asynchronously Called VI Stop Responding Without an Error

Updated Sep 10, 2026

Environment

Software

  • LabVIEW

My asynchronously called VI stops responding without generating an error or crash report.

This is in LabVIEW with Object-Oriented Programmin, using a Start Asynchronous Call.

Indirect recursive by-value object containment causing stack overflow.

To remove this issue 
  • break recursive by-value relationships
  • use reference-based communication
  • implement worker heartbeat monitoring
  • verify using synchronous execution
  • use DETT to confirm worker termination

Watchdog implementation is currently the recommended pattern.
Execution:State may not reliably detect a terminated worker thread when using strictly typed VI references.

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.