Stack vs Heap Memory - Simple Explanation
I take a look at Stack and Heap Memory and how it affects your application. Knowing how memory is handled in your application can help you understand your variables' scopes.
☕️ I don’t accept paid sponsorships and I have turned off mid-video ads. You’re welcome! If you would like to support my channel see: ko-fi.com/alexhyett
📨 Join my free weekly newsletter for advice, technology and more: newsletter.alexhyett.com
🗺️ Backend Developer Roadmap: www.alexhyett.com/backend-dev...
📝 Blog Post: www.alexhyett.com/stack-vs-he...
🎓 RECOMMENDED COURSES (Use code FRIENDS10 for 10% off)
The Complete Web Developer Course - academy.zerotomastery.io/a/af...
The Complete Junior to Senior Web Developer Roadmap - academy.zerotomastery.io/a/af...
Complete SQL + Databases Bootcamp - academy.zerotomastery.io/a/af...
📚 RECOMMENDED BOOKS
Software Development
Clean Code - geni.us/5AEwj2
Clean Architecture - geni.us/yBrTX
Domain Driven Design - geni.us/WiR0Q0x
Design Patterns - geni.us/5ncUt
Developer Hegemony - geni.us/lAXy
Pragmatic Programmer - geni.us/GfNj9
Data Structures and Algorithms Made Easy - geni.us/sqg6kJ
Refactoring - geni.us/ufAP0mE
The Productive Programmer - geni.us/IT9WiN
Pragmatic Thinking and Learning - geni.us/x81A
Test Driven Development - geni.us/HFV52
Microservices - geni.us/8vMA
🚀 MY FAVOURITE TOOLS
Visual Studio Code - code.visualstudio.com/
Obsidian - obsidian.md/
Notion - affiliate.notion.so/alexhyett
⏳ TIMESTAMPS
00:00 Introduction
00:18 Three main parts
00:28 Stack data structure
00:51 Call stack
01:19 Heap differences
01:50 Variable storage rules
01:58 Value types and reference types
02:23 Local variables
02:40 Reference types on heap
02:57 Value types on heap
03:20 Garbage collector
03:53 Exceptions to the rule
04:40 Asynchronous methods
You can check out more of my favourite tools on my website:
www.alexhyett.com/tech/
🔗 MY KEY LINKS
🌍 Blog - www.alexhyett.com/
🐘 Mastodon - social.alexhyett.com/@alex
🧑💻WHO AM I
I'm Alex, a Software Developer and KZhead working in the UK. I make videos about software development to help developers with the skills they need to be senior developers. As well as this KZhead Channel, I also write articles on my website (alexhyett.com) as well as write a regular newsletter that contains some thoughts to help aspiring developers.
‼️ DISCLAIMERS
Some of the links in this description are affiliate links, for which I get a small commission, at no extra cost to you 🙂. I appreciate you supporting my channel so I can continue providing you with free software development content!
#coding #programming #developer
These ideas were saved in my head as a sequence of words for the entirety of my undergrad. If 5 short minutes you managed to actually help me understand a huge gap in my understanding. Thank you so much.
You're welcome Michael, I am glad it helped.
@@alexhyettdev public class Main { String s = "ABC"; public static void main(String[] args) { Main obj = new Main() ; System.out.println(obj.s); } } in this above code String object is created in heap and also of class. So 2 objects in heap. But isn't the string object Abc resides inside class object in the heap?that's why we are calling it obj.s
Good video very in-depth
i feel the exact same way!! this random collection of words and statements now i feel like concrete concepts in my brain
Perfect, really good explanation. Thank you!
Finally a much simpler with actual sample code that explain the whole stack and heap stuff. Now I understand why and when OOM occurs in app, the usual suggestion is to increase heap size but said to be slow or when we do recursion recklessly we get stackoverflow.
hey this is an excellent video! i'd never thought or read about the link between variable scope and memory. thank you so much!
This video actually answered all my questions about how the stack and heap work together. Great explanation!
A nice and concise explanation . Wishing you all the best for better reach of your subsequent tutorials so a lot from community would benefit
This explanation was exactly what I needed! thank you Alex
You’re welcome I am glad it helped!
The analogy of a stack of books provided much needed clarity for me. I appreciate the video mate!
You’re welcome, I am glad it was helpful.
Alex, you made my day. I would call you one of the best instructors! Your explanations are flawless. You explain perfectly in context. For instance, where you explain why variables are not accessible outside the method.
Jake, you made my day! Thank you for the lovely comment. I am glad you found it helpful!
This is an excellent video about how the memory works, I love the last part about asynchronous methods. Thank you for this awesome content. I wish you could speak more about asynchronous functions. 😃
This is one of the best programming related videos I have ever watched. It cleared up so much of my confusion in C++.
Thank you!
Wow this was an incredible series of topics, thank you!
Thanks, I’m glad you enjoyed it!
Your explanations are immaculate! You'll definitely make it big if you want to. I am glad I caught your channel early at 18.4k subscribers
I appreciate that! Will be making more videos soon.
Not gonna lie, i cant state enough how explanations like this can massively improve your understanding of why code works the way it does. Just learning to code is one thing, but understanding whats behind all of it and WHY whatever thing actually is happening, can definitly up your game. Im not a pro by any means, but i think stuff like this is very important. The visual presentation also makes it way easier to follow and connect the concepts - so thx for that 😊
Thank you, I am glad you enjoyed the video. I find it helps with remembering everything as well. If you can understand something then it tends to stick in your mind a bit better.
hell yeah. idk how you did it but that finally made sense. i had to have heard the stack of books analogy before, but this is probably the first time seeing it played out with actual books imma have to watch this again
Thanks for this simple and straight to the point explanation
You’re welcome!
Reading a book right now that explains this concept rather poorly over 20 pages. You managed to grant me understanding in 5 minutes, and now I can continue reading past the chapter. Thank you, great explanation!
You’re welcome! I am glad I could help you understand it. Hopefully more fun than reading 20 pages of that book.
Dude, that was awesome. You explained what I tried to wrap my head around in college courses, in 5 minutes. ily :)
Thank you! 👍
Such an intuitive and simple explanation!
Thank you, I am glad it was helpful.
Very well explained. Thank you!
Thank you, I am glad you liked it!
A hidden gem !!! Thanks you so much, I understand it so much better now !!!!
I am glad it helped!
That is a great, clear, and easy explanation, thank you.
absolutely brilliant explanation, thanks a lot
Thanks, I am glad it was useful!
Excellent explanation. Thank you so much.
The best explanation/animation ever.
Thank you!
Thank you for easy to understand and great video
Great tutorial, it really helped me! Keep it up👍
Thank you! I am glad you found it helpful.
Simply love your explanations.. Clean and deep..
Thank you! 🙏
Great explanation! Thanks Alex!
You’re welcome!
Great explanation. I do mostly web development, but I've been getting into low-level programming recently, and your video really helped me reach out into my bucket of programming concepts and rearrange a bunch of previous knowledge I had about computers into something more clear and concise. Thanks!
You're welcome, glad I could help!
This video was very good! I really like the way you explain!
Thank you! I am glad you liked it.
Really great video! This helped so much
Thank you I appreciate the kind words. I am glad it was helpful.
lovely explanation, thank you for this
You’re welcome! I am glad it was useful.
Thanks for the great explanations!
Loved the explanation !
Thank you! I am glad it was helpful.
Excellent breakdown!
Thank you!
Thank you very much i was not able to understand this concept even after reading and watching a lot of videos now i have a good understanding of this
That’s great! I am glad I helped.
@@alexhyettdev if possible can you please explain the anonymous function part i didn't get it
That's good stuff ❤ subscribed
that was a clean description of stack and heap. Never knew about anonymous function being a heap, but it makes sense
Thanks I am glad you liked it 👍
Fantastic explanation, thanks mate!
You’re welcome! I am glad you liked it.
Thank you! This was great
you actually help me understand a lot ,thank you sir
You’re welcome!
Very nice explanation. Thanks !
@Alex Hyett As always, you give the best explanation of whatever programming topics that you cover. Please keep up the great work and keep the content coming. I'm a fan :)
Thank you, I am glad you like them!
Excellent explainer and graphics THX
You’re welcome, I am glad you like it.
amazing, this help me understand everything
Well done! Very good video.
Thank you sir. Good Explanation. Please, I wish you make a video on "Why in Java, Do Local Variables Used in Lambdas Have to Be Final or Effectively Final?" and please make the explanations at the memory level too, so we can understand all the mechanics behind it.
This is good. Have learned some things I could not know in a year.
That’s great I am glad you learned something from it. Thank you for commenting.
Such a great explanation
Thank you! I am glad you liked it.
Hey man, awesome awesome tutorial
Thank you!
Finally, i now understand the differences between these two. Thank you for the video
You're welcome 😊
Create more content, you'll be to a million subscribers within a few short years I have no doubt. Your content is pure gold, thank you for explaining this so clearly.
Thank you 🤞🏻. Regular content will be back again in September. I have had some family commitments that has put a stopper to my videos this month.
@@alexhyettdev fully understand. Good luck! I quit my full time job as a mechanical engineer to become a programmer/coder of sorts. Bit tough being a student at age 41 but for me I made the decision to ultimately spend more time with my family. Have a super day further.
thank you! very clear
You're welcome Julia, thank you for commenting.
Learning Redux right now, so very helpful! Definitely subscribing.
Awesome, thank you!
Nice video, very helpful
You’re welcome, thanks for commenting.
My jaw dropped when you explained what happens to variables declared in the stack, I never made the connection between this fact and the scope of variables, thank you soooo much !!!
Samee heree, I've never even thought of why we couldn't call variables from different scopes, i just took it for granted this opened my eyes
I'd be extremely weary of taking this for fact. It is up to the compiler to generate scoping rules, as far as I know. Look into it a bit more.
Thank you very much mate. Clear : )
Awesome video! Id like to add that in csharp async doesnt always equal multithreading, and since it uses internal statemachine which is a class, asyncs may get allocated on the heap
Yes it’s a good point!
that was flawless thanks a million man
You're welcome, I am glad you liked it.
Great explanation!
Thanks! I’m glad it was helpful!
Man you're a savior thanks for the clear explanation
Thanks, glad I could help
Thanks for the video
You’re welcome!
You're great. Thanks
How does garbage collection handle memory fragmentation? Is there a heap defrag utility? Do you wipe the heap when a program ends? What is multiple programs / threads run concurrently? Now I need to check the rest of your videos for answers. Thank you for starting my journey.
Great video!
Nice video pal. I love to see a video about boxing and unboxing.
Thanks! Sure I will add it to my list.
Thank you!
You're welcome, I am glad you liked my video.
this video is gold! wow!
Thank you!
neat explanation, ty
Thank you. Thanks for commenting!
Amazing explanation, greetings from Chile
Thank you! Hi 👋 from UK 🇬🇧
thanks for your video
You're welcome, I am glad you liked it!
Good video. One question: In the case of results from asynchronous methods, once the asynchronous function completes, who cleans up the result in the heap that was left over by the async function?
Generally they will be cleaned up by the garbage collector in the same way other objects on the heap are.
@@alexhyettdev thanks for your response
Incredible. Even though I've been a professional developer for six years, I was having a crisis of confidence tonight because I've worked with languages where I never have to worry about this directly. I was asking myself, "Do I even know anything about computers if I don't know the difference between the stack and the heap?" Five minutes and twenty-seven seconds later, I feel like I have a solid understanding of the difference and I'd be capable of talking about this intelligently. Thank you 🙏
I have been a developer for 12 years and I went through exactly the same thought process before making this video. I am really glad it helped you.
Same here just went through a training where some memory management stuff was covered and I felt like an imposter. This made it all make sense
Loved the garbage collector animation. Very nice and funny
thanks dude
Such a precious channel!!! Instant sub from me 🍻🍻
3:01 small correction. A const is NOT allocated on the heap. In fact, it's embedded on the call site at compile time (in C#/F#/VB), the reference is removed (you can test this: create a const in another lib, reference and use it in your lib. Compile. Now update the const in the referenced lib and recompile, but do not recompile your lib. You'll see it did not change on the call site). What you probably want is readonly, which, in your example at 3:01, would then be allocated on the heap.
Many thanks to your video, this KZhead is valuable, so I read word by word carefully. And I find at 03:55, about the static variable, which is different from what you mentioned in your flvog (the link you provide in descriptions). In ur flvog, in para "where do static variable live", there you said static variables even if they are value types are not stored on the stack or the heap...need clarify? Thanks.
Thanks for spotting the discrepancy! I need to update my blog to make things clearer. Basically it is an implementation detail. In C# static variables are part of the MethodTables on the "High Frequency Heap". Which is a special part of the Heap memory for static variables and internal data structures. In C and C++ they are stored on the Data Segment, which is a special part of the memory for storing static variables and internal data structures. :) Sound familiar? If you look up Data Segment and High Frequency Heap they are both in the same place in memory. By the looks of things they are just slightly different implementations of the same thing. There is an old article here that explains it in depth: web.archive.org/web/20140724084944/msdn.microsoft.com/en-us/magazine/cc163791.aspx Jon Skeet also has a good article on it as well: jonskeet.uk/csharp/memory.html
@@alexhyettdev Thanks for your response and your KZhead.
Brilliant video
Thank you!
Nice explanation :)
Thanks 🙂
thank you.
You’re welcome!
Great video
Thank you!
Love how clear and concise this was! Subscribing. Just a note, it might be helpful to mention how in C there is no garbage collector and you have to free the memory yourself.
Thank you! Yes good point C and C++ (and of course Assembly) don't have a garbage collector. As far as I am aware all the others do but there might be a few exceptions!
God bless you man.
Thank you! 🤩
Great Vid
@4:23 what do you mean by the anonymous function is pushed on top of the stack and not have access to what previous level down? You mean even variables within main?
This video needs to be promoted higher on KZhead. Anyone who wants to learn Rust should start from here before diving into the borrow checker.
Thank you. I am glad it is useful for people learning Rust as well. Some of the C# references might not be applicable but hopefully the rest is. I need to learn rust as well actually!
you are the king
Thanks man 👑!
Noice explanation thanks mate
Glad it helped
Very good video
Thank you! I am glad you enjoyed it.
Can you recommend 2 or more books on memory and data structures?
awesome
Thank you!
what does "heap has higher overheads" mean...? higher cost? I assume (seeing that little 'watch' with pointer at high) that you mean for example it's slower, because it's more complicated for the "machine code" to add to the heap?
Yes higher overheads as in performance. It is slower to add to the heap compared to the stack.
Hello sir at 3:20 in the video you say that in must run times there is a garbage collector that will clean the memory from the stored memory location after it has finished execution. Not sure if you know but with in C and C++ language we do not have a garbage collector I was told. So in C and C++ we delete pointers manually after block execution. So, Actually C and C++ are not garbage collecting languages.
Great explanation! Thank you! My only bit of feedback would be to stay on the graphic visualizations longer. The constant switching between the visualizations and the shot of you talking is a bit jarring and makes it harder to focus.
thank you
You're welcome!
very nice video
I haven't coded in over a year. I had a dream where I was traversing a world on some quest to explain stack vs heap to all these people getting it wrong, and I knew they were wrong but didn't know why. Soon as I woke up I came here. Now I can sleep at night again. Thanks! 😂 It was an..(Explain you're a nerd without saying you're a nerd XD)... moment.
I am glad I can help you sleep at night! 😂
Can you re-check this one? I think something is incorrect with global or static variables. We basically have 4 segments: Stack, Heap, Code Segment, and Data Segment. Global or static variables, including constants like `const int MAX_AGE = 99`, are not stored on the heap. They are typically stored in the Data segment of the memory, specifically in the initialized data section. The Data segment is a part of the memory that contains static and global variables. These variables are allocated and initialized before the program starts executing. The initialized data section of the Data segment holds variables that have explicit initial values, such as the MAX_AGE constant in your example.