extern/zrepl
1
0
Fork 0
mirror of https://github.com/zrepl/zrepl.git synced 2024-11-28 19:34:58 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Created Debugging (markdown)

Christian Schwarz 2019-09-08 09:47:31 +02:00
parent 0d88081efb
commit aeb5c246a6
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Debugging.md Normal file

@ -0,0 +1,17 @@
## Memory Leaks & Goroutine Leaks
A good example for a goroutine & memory leak caused by not draining a channel is
[3bfe0c16d0233cac66a01a6f89959c34ef01c663](https://github.com/zrepl/zrepl/commit/3bfe0c16d0233cac66a01a6f89959c34ef01c663d) ("rpc/dataconn/stream: fix goroutine leaks & transitive buffer leaks")
1. Run zrepl with autostarted pprof server: `ZREPL_DAEMON_AUTOSTART_PPROF_SERVER=:12345 zrepl daemon`
(We will assume the address is 192.168.124.252)
2. `watch 'curl 192.168.124.252:22345/metrics | grep -v "#" | grep memstats'`<br/>
=> `go_memstats_heap_inuse_bytes` or `go_memstats_heap_alloc_bytes` should be rising
3. `watch curl http://192.168.124.252:12345/debug/pprof/goroutine?debug=1`
```
9 @ 0x469db0 0x43d5f4 0x43d5ca 0x43d355 0xc767b0 0x498f51
# 0xc767af github.com/zrepl/zrepl/rpc/dataconn/stream.doWriteStream.func1+0x2ff /mnt/zrepl /rpc/dataconn/stream/stream.go:92
```
=> 9 kept increasing to higher numbers over time => look at `doWriteStream` impl and fix goroutine leak (see commit)