Code With Go
  • Code With Go
  • 01. What, Who, Why and Where?
  • 02. Compiled vs Interpreted languages
  • 03. Types of Type!
  • 04. Stack and Heap Memory
  • 05. Garbage Collection
  • 06. About Go
  • 07. Go Playground
  • 08. Hello, World!
  • 09. Installing Go
  • 10. Variables
  • 11. Constants
  • 12. Integers
  • 12. Floats
  • 13. Boolean
  • 14. Strings
  • 15. Complex Numbers
  • 16. If Else
  • 17. Switch
  • 18. For
  • 19. User Defined Types
  • 20. Arrays
  • 21. Slices
  • 22. Structs
  • 23. Maps
  • 24. Functions
  • 25. Defer
  • 26. Pointers
  • 27. Methods
  • Resources
    • Resources - Paid
    • Resources - Free
Powered by GitBook
On this page
  • Comparison of Stack and Heap memory
  • Gophercon - Understanding Allocations: the Stack and the Heap - GopherCon SG 2019
  • Blog Posts

Was this helpful?

04. Stack and Heap Memory

A simple comparison

Previous03. Types of Type!Next05. Garbage Collection

Last updated 5 years ago

Was this helpful?

Comparison of Stack and Heap memory

Stack Memory

Heap Memory

Generally, memory is automatically managed by program.

Generally, memory management to be done by programmer.

Traditionally used to stores temporary variables created by each function.

Variables created on the heap are accessible by any function, anywhere in program.

Limit on stack memory size.

No specific limit on heap memory size.

Self cleaning memory.

Memory cleanup required explicitly.

Gophercon - Understanding Allocations: the Stack and the Heap - GopherCon SG 2019

Blog Posts

Like C, Go uses both stack and heap memory. How can a Gopher know which is being used?
Understanding Pointers and Memory Allocation
Logo