ue-async-threading

Unreal Engine async patterns like UE::Tasks::Launch, Async, and FAsyncTask dispatch CPU-bound work to background threads, returning results to the game thread via synchronization primitives and weak pointers to prevent data races.

Safe UObject access from async tasks requires weak pointers and strict lifecycle management to prevent background threads from dereferencing garbage-collected objects, avoiding data races and crashes.

Use ParallelFor for data-parallel iterations over collections, and FRunnable for persistent background threads requiring custom lifecycle management, both safely offloading CPU work from the game thread.

TaskGraph and UE::Tasks::Launch coexist for concurrency: TaskGraph manages complex dependencies and prerequisites, while UE::Tasks::Launch executes lightweight fire-and-forget background tasks for scalable game logic.

Data races and crashes occur when async tasks lack synchronization primitives or weak pointers. Implement atomic safeguards and thread-safe data to protect shared variables across concurrent operations.

Dispatching async results back to the game thread requires synchronization primitives, proper lock usage, and atomic safeguards to ensure thread-safe data delivery without violating UObject access rules.