What can lead to memory leaks in Go?

Memory leaks in Go can occur despite the garbage collector for several reasons:

• Long-lived references: if objects remain accessible through references, the garbage collector will not delete them.
• Global variables and singletons that accumulate data.
• Closures capturing large objects.
• Channels and goroutines that are not closed or blocked, holding onto memory.
• Unbounded caching, leading to increased memory usage.

Example: if elements are added to a slice and it is not cleared, memory will grow:

var cache []byte
func addData(data []byte) {
    cache = append(cache, data...)
}

It is important to control the lifecycle of objects and use memory profiling (pprof) to identify leaks.