"If a worker wants to do his job well, he must first sharpen his tools." - Confucius, "The Analects of Confucius. Lu Linggong"
Front page > Programming > Does Deleting a Map Entry Lead to Memory Leaks When Holding Pointers?

Does Deleting a Map Entry Lead to Memory Leaks When Holding Pointers?

Posted on 2025-02-06
Browse:631

Does Deleting a Map Entry Lead to Memory Leaks When Holding Pointers?

Does Deleting a Map Entry Cause Memory Leaks?

Introduction:
In a recent discussion, it was raised that deleting elements from a slice of pointers could potentially lead to memory leaks. This question extends that inquiry to maps, specifically whether deleting an entry from a map holding pointers results in similar behavior.

Checking the Implementation:
To determine the truthfulness of this claim, let's investigate the source code for map deletion in Go's runtime: runtime/hashmap.go (function mapdelete()). Examination reveals that both the key and value are cleared upon deletion (#600, #602).

Zeroing Implications:
Clearing these values effectively severs the connection between the map and the pointed objects. This ensures that even though the values themselves may be pointers, the map no longer references them. As a result, the pointed objects become eligible for garbage collection if they have no other references.

Practical Example:
To verify this behavior, let's construct a test case:

type point struct {
    X, Y int
}

var m = map[int]*point{}

func main() {
    fillMap()
    delete(m, 1)
    runtime.GC()
    time.Sleep(time.Second)
    fmt.Println(m)
}

func fillMap() {
    p := &point{1, 2}
    runtime.SetFinalizer(p, func(p *point) {
        fmt.Printf("Finalized: %p % v\n", p, p)
    })
    m[1] = p
    fmt.Printf("Put in map: %p % v\n", p, p)
}

Output:

Put in map: 0x1040a128 &{X:1 Y:2}
Finalized: 0x1040a128 &{X:1 Y:2}
map[]

In this example, the pointer value (p) is put into the map and a finalizer is set to be called upon garbage collection. After deleting the entry from the map and forcing garbage collection, the finalizer is invoked, proving that the pointer was indeed removed from the map.

Conclusion:
Based on the source code analysis and practical example, we can conclude that deleting an entry from a map of pointers does not cause memory leaks. The Go runtime ensures proper garbage collection by zeroing the cleared values, allowing the pointed objects to be reclaimed when no other references exist.

Release Statement This article is reproduced on: 1729686641 If there is any infringement, please contact [email protected] to delete it.
Latest tutorial More>

Disclaimer: All resources provided are partly from the Internet. If there is any infringement of your copyright or other rights and interests, please explain the detailed reasons and provide proof of copyright or rights and interests and then send it to the email: [email protected] We will handle it for you as soon as possible.

Copyright© 2022 湘ICP备2022001581号-3