mirror of
https://github.com/wolfpld/tracy.git
synced 2026-09-25 03:25:52 +00:00
Addresses the "server just vanishes" pattern from alandtse/tracy#2, where Unable to connect gives no way to tell a segfault apart from a hang and required manually killing an unresponsive process before restart. - faulthandler.enable() at startup writes a thread-state traceback to tracy_mcp.crash.log on a genuine fatal crash (works on Windows via SetUnhandledExceptionFilter). - The periodic sweep loop now also logs a heartbeat (uptime, instance/task counts, evictions) so a hung event loop is distinguishable from a dead process by the last timestamp on disk. - _is_our_server_running() now backs its os.kill(pid, 0) check with an HTTP self-ping. A deadlocked-but-alive process passed the old PID-only check, silently blocking restart; a non-responsive server is now reported by PID and a fresh instance starts on a new port instead.