ipfs/kubo

Add goroutine leak profile to `ipfs diag profile`

Open

#11,191 建立於 2026年2月10日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Go (13,906 star) (2,725 fork)batch import
P1effort/hourshelp wantedkind/enhancement

描述

Go 1.26 ships an experimental goroutine leak profiler (GOEXPERIMENT=goroutineleakprofile). It detects goroutines blocked on channels, mutexes, or conditions that can never unblock, using GC reachability analysis. Zero runtime overhead unless actively collecting.

Available at /debug/pprof/goroutineleak when enabled.

Proposal

Once 1.27 ships with it enabled by default:

  • Add a goroutine-leak collector to ipfs diag profile --collectors (gated on the experiment being available at runtime)
  • Expose it via the existing /debug/pprof/ endpoint on the API port

This would help diagnose daemon goroutine leaks without external tooling. Useful for long-running nodes where leaked goroutines accumulate over time.

References

貢獻者指南

技術棧
go
領域
observabilitytooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingunderstanding of pprof profiles
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
The issue proposes adding a goroutine leak collector to the `ipfs diag profile` command, gated on the Go experiment being available. Start by reading the Go 1.26 documentation on goroutine leak profiles and examining the existing collectors in the `ipfs diag profile` codebase (likely in a diagnostics package). Also review the `/debug/pprof/` endpoint implementation to see how to expose the new profile. The issue is waiting for Go 1.27 to enable it by default, but initial implementation can be done behind a build tag. Check if there are any linked PRs or comments for additional context.
Add goroutine leak profile to `ipfs diag profile` · ipfs/kubo#11191 | Good First Issue