debug-troubleshoot

Debugging Tokio deadlocks requires identifying lock contention and async task blocking using tracing instrumentation and Tokio Console. Enable tracing spans around lock acquisition, set timeouts on critical sections, and use Tokio Console to visualize task states and detect tasks waiting indefinitely on locks or channels.

Diagnose connection problems by implementing health checks on Turso and redb clients, logging connection lifecycle events with tracing, and monitoring for exhausted connection pools. Check database availability, validate credentials, and trace query execution to pinpoint where connections fail or hang.

Capture panics in async services using tracing to log panic context, backtrace, and task information before the panic propagates. Integrate with panic hooks, use LLDB or GDB to inspect memory state at crash time, and correlate panic timing with tracing spans to identify the triggering condition.

Memory leak detection in Tokio services combines tracing to track resource allocation and cleanup, heap profiling with tools like Valgrind or heaptrack, and LLDB/GDB inspection of live processes. Monitor task lifetimes, connection counts, and buffer sizes to identify resources not being released.

Effective async debugging requires tracing crates for structured logging, Tokio Console for runtime introspection, and debugger integration with LLDB or GDB. Install tracing subscribers, enable Tokio Console support in your async runtime, and configure debugger symbols to inspect task state and lock contention.

Performance troubleshooting uses tracing to measure span durations, Tokio Console to identify task scheduling delays and work-stealing inefficiencies, and profilers to find CPU or I/O bottlenecks. Correlate slow traces with database query latency on Turso or redb, and check for blocking operations on the async executor.