FlameGraph on Mengboy 技术笔记

Go Memory Leak Triage in Production: pprof + FlameGraph Step by Step

Sat, 14 Feb 2026 21:20:00 +0800

If your Go service RSS keeps climbing, drops after restart, then climbs again, you likely have a memory retention problem (or an actual leak pattern).

Do not start with random code edits. Run a clean evidence chain: metrics trend check → pprof snapshots → FlameGraph comparison → object growth path → regression validation.

Go 服务内存泄漏定位实战：pprof + FlameGraph 一次找准

Sat, 14 Feb 2026 21:20:00 +0800

线上 Go 服务 RSS 一路涨，重启后短暂恢复，过几小时继续涨——这就是典型“疑似内存泄漏”场景。

别先拍脑袋改代码，先把证据链跑通：监控确认 → pprof 采样 → FlameGraph 对比 → 定位对象增长路径 → 回归验证。这套流程跑完，基本能把“玄学泄漏”打成“可复现 bug”。