gpui-context

To manage GPUI context across App, Window, and async tasks, you centralize state and coordinate updates using App, Window, Context<T>, AsyncApp, and AsyncWindowContext. This covers global initialization, per-window rendering, and component-level updates.

Spawning async tasks safely in a GPUI window requires using AsyncWindowContext to preserve lifecycle awareness. This approach orchestrates background work and entity updates without causing memory leaks during window rendering.

Triggering a UI re-render in GPUI involves reading and updating the entity through its Context<T>, then calling notify. This invalidates the component-scoped context and coordinates the window rendering pipeline.

Use AsyncApp for background tasks tied to the global application lifecycle, and AsyncWindowContext for tasks scoped to a specific window's rendering and state. This distinction ensures safe asynchronous task orchestration without leaks.

Yes, GPUI context management supports per-window entity lifecycle coordination through Window and AsyncWindowContext. These contexts manage state, trigger re-renders, and handle background work specific to each window.

Async tasks cause state leaks in GPUI window rendering when spawned outside lifecycle-aware contexts. Using AsyncWindowContext or AsyncApp ensures safe entity management and coordinates updates without leaking memory.