I found that my IPFS would cause a large number of memory leaks after running for a period of time, so I used the go tool pprof ipfs.heap to analyze it. May I ask if you have encountered the same situation before, or what operation caused these memory leaks, and how to avoid them
go tool pprof ipfs.heap
File: ipfs
Build ID: 957c4935f18c61c943d7fd70f5daa89cc3833e52
Type: inuse_space
Time: Oct 17, 2024 at 9:03am (UTC) Entering interactive mode (type "help" for commands, "o" for options) (pprof) top 10
Showing nodes accounting for 742.45MB, 94.65% of 784.42MB total
Dropped 157 nodes (cum <= 3.92MB)
Showing top 10 nodes out of 123
flat flat% sum% cum cum%
340.32MB 43.39% 43.39% 340.32MB 43.39% github.com/ipfs/go-merkledag.(ProtoNode).Copy
329.27MB 41.98% 85.36% 329.27MB 41.98% google.golang.org/protobuf/encoding/protowire.AppendBytes (inline)
19.02MB 2.42% 87.79% 355.29MB 45.29% github.com/ipfs/go-merkledag.(ProtoNode).marshalImmutable
Checklist
Installation method
built from source
Version
Config
Description
I found that my IPFS would cause a large number of memory leaks after running for a period of time, so I used the go tool pprof ipfs.heap to analyze it. May I ask if you have encountered the same situation before, or what operation caused these memory leaks, and how to avoid them
go tool pprof ipfs.heap File: ipfs Build ID: 957c4935f18c61c943d7fd70f5daa89cc3833e52 Type: inuse_space Time: Oct 17, 2024 at 9:03am (UTC) Entering interactive mode (type "help" for commands, "o" for options) (pprof) top 10 Showing nodes accounting for 742.45MB, 94.65% of 784.42MB total Dropped 157 nodes (cum <= 3.92MB) Showing top 10 nodes out of 123 flat flat% sum% cum cum% 340.32MB 43.39% 43.39% 340.32MB 43.39% github.com/ipfs/go-merkledag.(ProtoNode).Copy 329.27MB 41.98% 85.36% 329.27MB 41.98% google.golang.org/protobuf/encoding/protowire.AppendBytes (inline) 19.02MB 2.42% 87.79% 355.29MB 45.29% github.com/ipfs/go-merkledag.(ProtoNode).marshalImmutable