You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here, parent refers to child, and child refers back to parent. This creates circular references that can cause memory leaks, because the garbage collector in Go will not be able to detect that the object is actually no longer used.
Maybe it won't happen, but right now I'm still researching
if it's real maybe the solution is :
Weak References
stopping reference manually when no needed
change structure to traversal graph
using Runtime Finalizer
The text was updated successfully, but these errors were encountered:
go-map-validator/map_validator/tree_chaining.go
Line 7 in 5bd51d5
Here, parent refers to child, and child refers back to parent. This creates circular references that can cause memory leaks, because the garbage collector in Go will not be able to detect that the object is actually no longer used.
if it's real maybe the solution is :
traversal graph
Runtime Finalizer
The text was updated successfully, but these errors were encountered: