Stack Memory vs Heap Memory [duplicate]

by

In C++ the stack memory is where local variables get stored/constructed. The stack is also used to hold parameters passed to functions.

The stack is very much like the std::stack class: you push parameters onto it and then call a function. The function then knows that the parameters it expects can be found on the end of the stack. Likewise, the function can push locals onto the stack and pop them off it before returning from the function. (caveat – compiler optimizations and calling conventions all mean things aren’t this simple)

The stack is really best understood from a low level and I’d recommend Art of Assembly – Passing Parameters on the Stack. Rarely, if ever, would you consider any sort of manual stack manipulation from C++.

Generally speaking, the stack is preferred as it is usually in the CPU cache, so operations involving objects stored on it tend to be faster. However the stack is a limited resource, and shouldn’t be used for anything large. Running out of stack memory is called a Stack buffer overflow. It’s a serious thing to encounter, but you really shouldn’t come across one unless you have a crazy recursive function or something similar.

Heap memory is much as rskar says. In general, C++ objects allocated with new, or blocks of memory allocated with the likes of malloc end up on the heap. Heap memory almost always must be manually freed, though you should really use a smart pointer class or similar to avoid needing to remember to do so. Running out of heap memory can (will?) result in a std::bad_alloc.

More Related Contents:

  1. How to judge an address as legal or illegal by it‘s numerical value？ [closed]
  2. Dynamic memory allocation in game server [closed]
  3. When and why will a compiler initialise memory to 0xCD, 0xDD, etc. on malloc/free/new/delete?
  4. What is memory fragmentation?
  5. stringstream, string, and char* conversion confusion
  6. General guidelines to avoid memory leaks in C++ [closed]
  7. How to read file content into istringstream?
  8. Difference between pointer to a reference and reference to a pointer
  9. Create new C++ object at specific memory address?
  10. What is a glibc free/malloc/realloc invalid next size/invalid pointer error and how to fix it?
  11. What happens when a computer program runs?
  12. How do you determine the size of an object in C++?
  13. How do you read directly from physical memory on Windows?
  14. Could I ever want to access the address zero?
  15. What are uses of the C++ construct “placement new”?
  16. Read process memory of a process does not return everything
  17. Multithreaded Memory Allocators for C/C++
  18. Where are member functions stored for an object?
  19. Can I Allocate a specific memory address using pointers in c++?
  20. Is std::vector memory freed upon a clear?
  21. How can i estimate memory usage of std::map?
  22. When is a type in c++11 allowed to be memcpyed?
  23. Is global memory initialized in C++?
  24. Heap corruption under Win32; how to locate?
  25. Linux Allocator Does Not Release Small Chunks of Memory
  26. Dereferencing deleted pointers always result in an Access Violation?
  27. C++11: Replace all non-owning raw pointers with std::shared_ptr()?
  28. C++ virtual function table memory cost
  29. How to ignore false positive memory leaks from _CrtDumpMemoryLeaks?
  30. How to get the starting/base address of a process in C++?

Leave a Comment