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.