How does the garbage collector work and which memory areas does it clean: heap or stack?

Garbage Collector in Go automatically frees memory that is no longer used by the program. It works with the heap memory area, where dynamically allocated objects are placed.

The stack is a memory area for local variables and function calls, which is managed automatically when entering and exiting functions, and the garbage collector does not clean it.

The garbage collector in Go operates based on a reachability tracing algorithm: it finds all objects accessible from root points (stack, global variables) and deletes those that are no longer referenced.

Thus, the garbage collector cleans the heap, while the stack is managed by the call system and is freed automatically.