28-maps-memory-leaks/

[giscus[bot]]

28-maps-memory-leaks/

None

https://100go.co/28-maps-memory-leaks/

[fseda]

Are there any drawbacks to storing pointers instead of the actual value?

[scooby]

There are the usual problems with using pointers: you have to guard against nils, accessing values requires another pointer dereference, and it puts more load on the GC.

[nurjamil]

does it still happening after go 1.21 ?

[scooby]

Yes, maps still don't automatically release memory.

[LordMoMA]

why 1.16 does not have this problem?

[LordMoMA]

i did not see this issue after 1.23

[LordMoMA]

tested with:

➜  go-learning gvm use go1.16
Now using version go1.16
➜  go-learning go run .
Alloc = 0 MiB
Alloc = 461 MiB
Alloc = 0 MiB

even 1.16 did not have this problem.

[vincenshen01]

It's very useful for me to understand underlaying principles of golang.

[AmanKhys]

I went along with the code and you're wrong about it as of date.
The GC has fixed this and after deleting all the elements and then running a runtime.GC()
it clears everything.

One way to help me out, an internship offer if possible working with go.
[email protected]