What ACTUALLY happens during a Stack Overflow?

[@K1L0W0G]

The explanation is straight to the point, detailed and correct. Without begging for likes and subscribers. And with good aesthetics/editing. This is my new favorite KZbin channel.

[@Splarkszter]

Agreed. The quality is incredibly high.

[@user-pj9vw8ic3v]

forgot one very important detail... 😏

[@Billabongbabalog]

@@user-pj9vw8ic3v ...

[@furkankaraslan9040]

@@user-pj9vw8ic3v or two hehe

[@LunaticEdit]

Wow, someone who actually knows what they're talking about. Accurate, concise, and to the point. Excellent job.

[@troybird8253]

SIMP

[@TheOnlyJura]

Does she? She did not mention how exactly does a stack overflow get triggered (page fault exception, which happens when accessing a guard page). But I get that not everybody wants to be truly knowledgeable.

[@homomorphic]

​​@@TheOnlyJura she just said that the operating system terminates the process which is correct, since the exception vector points into kernel code. Having seen few of her other videos, I'm quite confident that Laurie could explain how the hardware generates the exception and how the kernels handler works, but covering how a program is terminated and unloaded from memory at a detailed level is a whole series of videos by itself.

[@MaxProgramming-uv6br]

Can we stop a moment to thank Laurie for the amazing theme that she has ? Whether the room or the frame they both are amuzing.

[@yurisich]

I like the juxtaposition of low level concepts from a security engineer known for writing ASM, on a Windows XP VM, using an website to do hex calculations, and a Google search to divide by 1000. And the vi/notepad++ use. It's all so random, but it feels very much planned.

[@arossfelder]

I think it's WIndows 10 tho :)

[@bazylicyran7727]

Exactly this, it really fucks with my mind. Such a well done video though.

[@Haegarrnc]

@@bazylicyran7727 it’s probably software from Stardock with an XP theme.

[@user-uf4rx5ih3v]

I think this is part of her channel branding. Personally, I could have done away with the whole algebra section but yeah.

[@b0ntr4g3r3]

And in the closing screens it looks like a MacOS running a windowed game of Burnout!

[@Drewer]

No Click bait, pure video teaching about stack overflow, well done!

[@Zappexe]

7:12 People might get the wrong idea that you are allocating memory in the stack as you push. Instead, you are pushing and poping data in the stack which is already percolated and is of fixed size - it's like a fixed-size array where the stack pointer is like an array index. Despite that, great video!

[@theRPGmaster]

"Percolated" 😄

[@Zappexe]

@@theRPGmaster ups :D

[@TheBypasser]

Technically there is no such a thing as "memory allocation", it is just a language concept ;)

[@InservioLetum]

You must never pope data. Data poping is haram.

[@homomorphic]

Stack *is* allocated on demand. The 8MB of stack referenced in this video is not 8MB of physically reserved memory, it is just 8MB worth of unbacked virtual addresses and as each unbacked address is read or written to, there is an exception and the OSs exception handler then allocates (one page at a time) the physical memory to that page (populates the page table).

[@sasan8822]

Great video. The only problem is the blue font on the terminal is not very visible on a black background.

[@lauriewired]

Yeah I noticed that 🥲 will fix it in future videos

[@GaryChike]

My eyes are black and blue now @@lauriewired

[@Haegarrnc]

@@lauriewired can’t fault you for it, it is the default for Linux. You should look at the “cool-retro-term” project. It might not fit with the theme of your videos but if you want a retro feel to your terminals then you can’t be it.

[@dannfr]

upgrade that eye

[@JohnsonSmithson]

@@dannfr his vision is not augmented.

[@Damon970]

This young lady's voice is very nice to listen to and learn. Thank you, Laurie.

[@pepijn_m]

A year ago her voice was lower then it is now. I am curious why she changed it/what's her normal tone.

[@JoRoBoYo]

@@pepijn_mhuh, i watch her first video, she is struggling to speak and breathe, from that i conclude this is her real voice

[@asdfjoe12]

@@JoRoBoYo I'm curious if she's a trans. She does seem to have some level of masculine characteristics.

[@BigAl7976]

Easy on the eyes too

[@upsilondiesbackwards7360]

​@@BigAl7976 You're pathetic.

[@archivethearchives]

Cool aesthetics. You definitely have that finesse for themes and your speech is so clear. Cool video.

[@aazjo]

Laurie, you have just the right amount of computer nerd, videographer, super awesome programmer, and mad computer scientist to make me wish one of my daughters had turned out like you. Keep it up! I'm a computer scientist and appreciate your well rehearsed explanations of these often hard to understand concepts.

[@Cm0nd00d]

your daughters are probably amazing, daughters are the best

[@BlackxesWasTaken]

With every single video I'm so delighted how well spoken you are. No ehm, like or similar. It feels really good listening to you describing the topic

[@strelkan]

listening and looking good too!

[@LuisAPeregrina]

@@strelkan 1 googol% agree.

[@xydez]

It's a script and good production, one should not underestimate the work that goes into making a video like this. It's well produced though, imo.

[@b43xoit]

That's right -- the absence of noise-vocalizations makes the speech easier to hear and understand and shows respect for the audience and self-respect.

[@Ne-lm7dy]

your channel is really cool, your editing and teaching skills for low code are the best I've seen on youtube, I'm learning a lot thank you

[@vectoralphaSec]

This is one of the top 3 best channels in the Computing/ Programming community here on KZbin.

[@joseph-montanez]

Another god-tier level video! Thank you so much everything you do and all the effort you put into these video!

[@Slycooper2456]

Yet another fantastic video! The stack usage visualizer really nails down the concept and makes it crystal clear. Great job!

[@notafbihoneypot8487]

Ready to stack this knowledge

[@Jool4832]

until it overflows.

[@uncleswell]

Mine was popping as it pushed. I'm left only with the last 5 seconds of the video :/. Gonna rewatch with a queue.

[@fyoutube2294]

Here dawg, you can place it right next to my stack of bread

[@notafbihoneypot8487]

@@fyoutube2294 I do love bread

[@mytechnotalent]

Great visual Laurie! It really helps solidify how the stack grows down as it grows toward the heap great graphic!

[@cl0udbear]

Great video and I really appreciated both the pace and the consistency of the pace. It was exactly the right rate of information the entire way through and at no point did I feel like speeding the video up or wandering into the comments and missing anything.

[@Kaiymu]

Thank you very much, I'm a software programmer but on the high level side, so I've never fully understood the memory part ! It gets cleare after your video.

[@maxmustermann5590]

Yo this channel is criminally underrated. You're not only really knowledgeable, but also great at explaining and very articulate. The algorithm should pick this up soon :)

[@ourinator692]

To be fair, the first video was only a year ago. Give it some time and she will grow very fast if she stays consistent.

[@munto7410]

Wow, your videos are really some of the best out there! I've never seen an educational video have this much personality. I can't wait to watch more!

[@VincentGroenewold]

Really clear, back in the day Assembly was a bit too much, but I appreciated it more and more. Even though it's not super productive. :)

[@gorak9000]

The lower level the language, and the harder it is to code, the more efficient the code will be in the end, because the programmer won't want to put the effort in to make it bloated adding extra junk. Now we have high level languages that people that have no idea what's going on behind the scenes and at the lowest levels code in, and layers upon layers of libraries and frameworks, and you end up with the bloated garbage that is pretty much all software these days. Because why write even the simplest thing from scratch in 5 lines of code when you can just use a 500MB library to do the same thing. I've seriously asked people in interviews that supposedly "know how to code" and supposedly have "data science" degrees the simplest most fundamental questions about Big Oh, and complexity, and they have not even the faintest whiff of an idea of what I'm talking about. All they know how to do is write glue code to glue various libraries together, and if it runs too slow, buy a bigger CPU.

[@fearisan]

​@@gorak9000I feel you, but it is simply incorrect to say high level = inefficient. A high level (language) gives the compiler more freedom to optimize. With low level code the programmer has to optimize by hand. Often times the compiler or interpreter can and will do a better job. A good example for this is SQL. It is a very high level language, yet extremely efficient at fetching data. Another example are JIT compilers which have knowledge about the actual architecture the code runs on and incorporate that into the compiled program. This works so well, that gcc added profile guided optimization. Another example is futhark which is a high level GPU computing language. Yes, you can likely write more efficient CUDA code by hand using shared memory and intrinsics but let me tell you that is a pain and a half in the beginning and futhark is plenty fast. Futhark allows you to more declaratively specify what it is you want calculated rather than telling the processor step by step what to do. Another example would be JSON encoding and decoding in Scala for which there are libraries which generate very efficient json (de-)serialization code using pseudo SIMD instructions (they load the data into a 64 bit long and use bit shift to parse the string very efficiently). The developer does absolutely not have to deal with this, the compiler will on their behalf. On that note: protobuf also is a high level language which gets compiled into very efficient code to (de-)serialization and nobody would want to write that by hand. If you factor in correct alignment to efficiently make use of CPU and I/O caches you better leave this task to a well written piece of algorithm than trying to reinvent the low level efficiency wheel all the time. Rust is another great high level example which gets compiled into very efficient code. Even haskell can run really fast even though it definitely is not a low level language. Thanks to referential transparency, the compiler can make assumptions about the code which it could not do otherwise and can produce efficient native code for the target platform. Even though you write haskell as if you couldn't mutate your data, thanks to referential transparency the compiler can turn this into very efficient code which may safely mutate state under the hood. This would not be possible if the developer were to write unsafe low level code because this takes away the guarantee for the compiler that this transformation is safe to do, Of course, just giving the opportunity to optimize to a compiler does not necessarily mean it will, but in general they do a great job. It is true, however, that many developers have only a surface level knowledge about what they are doing and are lost without google and stack overflow and it is those developers who write inefficient code which works ok enough for their small test data but absolutely explodes if fed anything of marginally interesting size.

[@fearisan]

​@@gorak9000I feel you 100% , but it is simply incorrect to say high level = inefficient. A high level (language) gives the compiler more freedom to optimize. With low level code the programmer has to optimize by hand. Often times the compiler or interpreter can and will do a better job. A good example for this is SQL. It is a very high level language, yet extremely efficient at fetching data. Another example are JIT compilers which have knowledge about the actual architecture the code runs on and incorporate that into the compiled program. This works so well, that gcc added profile guided optimization. Another example is futhark which is a high level GPU computing language. Yes, you can likely write more efficient CUDA code by hand using shared memory and intrinsics but let me tell you that is a pain and a half in the beginning and futhark is plenty fast. Futhark allows you to more declaratively specify what it is you want calculated rather than telling the processor step by step what to do. Another example would be JSON encoding and decoding in Scala for which there are libraries which generate very efficient json (de-)serialization code using pseudo SIMD instructions (they load the data into a 64 bit long and use bit shift to parse the string very efficiently). The developer does absolutely not have to deal with this, the compiler will on their behalf. On that note: protobuf also is a high level language which gets compiled into very efficient code to (de-)serialization and nobody would want to write that by hand. If you factor in correct alignment to efficiently make use of CPU and I/O caches you better leave this task to a well written piece of algorithm than trying to reinvent the low level efficiency wheel all the time. Rust is another great high level example which gets compiled into very efficient code. Even haskell can run really fast even though it definitely is not a low level language. Even though you write haskell as if you couldn't mutate your data which if executed naively would be inefficient, thanks to referential transparency the compiler can turn this into very efficient code which may safely mutate state under the hood. This would not be possible if the developer were to write unsafe low level code because this takes away the guarantee for the compiler that this transformation is safe to do, Of course, just giving the opportunity to optimize to a compiler does not necessarily mean it will, but in general they do a great job. It is true, however, that many developers have only a surface level knowledge about what they are doing and are lost without google and stack overflow and it is those developers who write inefficient code which works ok enough for their small test data but absolutely explodes if fed anything of marginally interesting size.

[@QW3RTYUU]

Because the big library is tested and maintained :) the 5 lines of code might have a deep rooted bug in it and if you do data science without tests, Id rather you use a bloated library than buggy code :)))

[@scraphex]

Let's all love Laurie!

[@BlackHermit]

Let Laurie love all!

[@GarfieldKartPMC]

simp

[@dxfate]

HUH

[@gatsu8634]

🎶 *I am ballin, I am faded* 🎶

[@NoiseCommander3DS]

I am developing a homebrew music-making app for the Nintendo 3DS and a stack overflow happened to me recently there. At first I thought my project was doomed and done for, it gave me quite a shock. After googling, I learned that 32kb are allocated by default and that it can be changed, so I allocated 128 kb instead. Phew... :D

[@pluto9000]

It might just take longer to overflow if you're pushing but not popping.

[@reeb3687]

i read that you were developing hebrew music

[@pluto9000]

@@reeb3687 😆

[@ThiemenDoppenberg]

😂@@reeb3687

[@xydez]

You might consider moving something to the heap instead - stack overflows are usually a sign of poor code. For example, you probably don't want to store the user's entire song on the stack, since it's used for the entire duration of the program anyways. Keep in mind that the main benefit of the stack is quick allocations and deallocations. Interesting project btw!

[@StevenOfWheel]

Came for the lit looks, stayed for the computer science

[@Haegarrnc]

Yeah, I’m completely turned on by her programming in Assembly but I’m learning new things too.

[@cardrivingdude]

For every thumbs up this comment receives, a thousand white knight gate keepers screech in total agony. lol

[@silvermeta2421]

fr this chick has crazy energy

[@pluto9000]

My stack is overflowing and she isn't going to pop it off 😩

[@cardrivingdude]

​@@pluto9000That's kinda cringe yo, ngl. Keep it classy kids!

[@picchioknossus8096]

OMG one of the very few youtubers that actually tells real content without BS, without showing unrelated stuff. Many tanks.

[@TheAussieRepairGuy]

Your clear articulation is far better than any programming channel I've ever watched. It's clear you have a good handle on the subject matter, but you may have lost touch with those who have a lesser grasp.

[@LelandMaurello]

Very cool! I learned a long time ago about using stacks, and how they overflow, and your explanation is right on point. Also you speak perfectly. Thank you LaurieWired!

[@JohnMcLaren-s2h]

Very clearly communicated and well edited video. Cheers Laurie

[@graytico]

Really glad i discovered your channel, as its quickly becoming one of my favorites

[@ravensthor9547]

Awesome explanation Laurie!

[@demonikidoff4613]

Everything about your videos is so cool and so well crafted... Such a great job !

[@renatoathaydes3162]

Not gonna lie, I was expecting just a python program that recursed forever. To see actual Assembly code, plus Python for GUI visualization, plus doing the calculation of how much memory each iteration was using, plus the use of an old-fashioned Solaris-like desktop... with nice informational popus at opportune times :D and the use of both vi and NotePad++!! You got a subscriber :).

[@brianhsu_hsu]

Wow, I like the visual theme of this video. Bring back so much memory of my childhood with computer. And the explanation is also very good and comprehensive. I really like it.

[@RhinoBlindado]

Excellent video! Very well researched, love that you put the code available and I absolutely adore the whole Serial Experiments Lain theme!

[@ThisIsJustADrillBit]

Woah im so glad i found this channel!! Super clean descriptions and very well laid out. Will be checking out the rest of your clips for sure!!! Thank you! 🔥❤

[@lllIIIlIllIIll]

Highly informative computer science ASMR, I love it ❤️ By the way this hairstyle looks fabulous, consider wearing it more often!

[@rorychivers8769]

I'm not really sure why, but suddenly the only thing I am interested in learning is what actually happens during a stack overflow.

[@garya1809]

Thanks for this it has helped solidify the concept in my brain. Computerfile has a "running a buffer overflow attack" video for the security perspective of this and how it is abused by threat vectors , so it was nice to see your video with more of the code exposed side of things.

[@TheManOfTheHourEveryHour]

Came for the pigtails. Stayed for the pigtails.

[@delibellus]

Thanks, Laurie! Your subjects are very good and you're really good at explaining. Quality content!

[@pcsecuritychannel]

It's been decades since I have seen that olive XP taskbar, I mean all the nostalgia videos have the blue one...

[@danielm.3832]

This was an incredible presentation and the UI is amazing!

[@garyjonjon]

This lady needs to be the face and voice of most instructional videos!

[@chauchau0825]

never expected but getting a deeper explaination than Uni

[@theata]

That was an amazing demonstration on how the stack works.

[@RIOTNOOB]

Its good to see younger coders that learn something

[@OceanusHelios]

Very clear and I am not even a coder. It was even clear and understandable watching it on 1.25 playback speed (faster).

[@martijn3151]

Perhaps a nice idea for a follow up is how does the CPU even detect an overflow? It’s just a pointer that gets lower and lower, what mechanism actually triggers a seg fault? And the stack size is something that can be set a link time; meaning you as a programmer have some control on its size, which can be handy if you expect your program to consume a lot of stack. Could be interesting to dive into as well. Just a thought.

[@jak3legacy]

She already explained that in this video, at least that is what I inferred. What you describe (detection of the segfault) is the very reason that the stack counts downward (or at least one of them). There is a "minimum" memory address that it can count down to, and it knows this minimum address in advance based on the initial allocation. The CPU is watching for that lower boundary memory address to become used, which is what triggers the seg fault.

[@bigp3t3_cpt]

Operating systems have a memory management components that use the MMU in the CPU to detect address violations but devs have to register an exception handler for it to be handled gracefully, otherwise the CPUs or OS send segfault to the process. If os is that process...

[@0x90h]

In big simplification when running process at user mode level it uses virtual memory instead of physical memory where virtual memory pages are mapped to physical memory addresses. Each virual memory page can be flagged as executable, readable or writable and other things (depending on CPU architecture and operating system). What happens when process creates new stack for thread ? There is allocation of virtual pages which are flagged as read and write and they are mapped linearly in process virtual memory space for example first page of size 4kb at address 0x40000000 second page at address 0x40004096, and so on but the page before the first allocated memory pages is flagged as not allocated or allocated and flagged as not for read and write therefore when CPU tries to access it, page fault exception is generated and cpu switches to execution page fault handler of operating system (some function in kernel mode which is executed when page fault happens). Operating system knows by analyzing active process and memory page address that it belongs to virtual memory page before stack beginning and then it generates stack overflow exception.

[@dixztube]

@@0x90hawesome. Any books you’d recommend to learn more on this

[@0x90h]

@@dixztube "Windows Internals" book Intel® 64 and IA-32 Architectures Software Developer Manuals wikiAosdevAorg // replace A with . Linux kernel source code

[@BenjaminWheeler0510]

Cool video! I like the use of assembly to explain “why” SOs occur: it’s the link reg! Not immediately obvious in C.

[@KelseyJacobson-zn3mw]

Your bangs are so freaking cute!!!!

[@jogizy]

deviant

[@infexis_95]

Gotta say, the Serial Experiment Lain theme you've got going is just amazing

[@ebojager]

Wow so glad I stopped to watch, I love your MacOS desktop theme and having your video in a window, looks amazing! Ive always wanted to know what a Stack Overflow was, thank you.

[@rsbah]

omg wow, I love your hairstyle 😍

[@surftheweb37]

Lucid, thorough and up to the point. Please, use some local calculator and value converter next time around (or at least host your own web instances of the said tools)

[@anonymoose9907]

Hello Laurie. I am very happy to finally be pointed by the You Tube algorithms towards women who have engineering smarts. Refreshing!

[@afrancis7475]

Homegirl is smarter than most of my teachers when I was a student. Even though I stopped coding a long time ago, this was a very enjoyable video. Your voice sounds a little bit like D.VA from Overwatch, so I feel like this channel is D.VA's side hustle 😂 Subbed!

[@OhhCrapGuy]

Interesting... I didn't realize that the stack grows down instead of up... That's actually really interesting. Btw, (extremely) minor point of accuracy, the Google byte/kilobyte converter is using base-10 kilobyte, while ulimit -s should be giving us base-2 kilobytes (kibobytes for those who prefer that nomenclature), meaning that the value of 315 KB it's giving us is very slightly wrong, or at least not as useful for comparing to the 8192 KiB value. The value it should have given us is actually 308 KiB. smh... Google is a tech company, they should know better than to default to base-10 units for bytes...

[@xydez]

*kibibytes but yeah good point, we really should standardize base 2, now its just a limbo

[@b43xoit]

Typical implementations of FORTH have the call stack and the operand stack growing toward each other from the two ends of one area of memory.

[@OhhCrapGuy]

@@xydez thanks, my phone kept "fixing" it for me and I missed the vowel

[@theharbingerofconflation]

Ah this is nice, I remember blowing other students minds in Uni when I showed them you can infer buffer sizes in most functions in C during callup since you already initialize the datastream somewhere. I avoided using malloc in my entire uni life and never had a single overflow. People outsource their brain to much to their language

[@VishwajithSaminathan]

that visualization is so sick.

[@HoSza1]

Imagine Powerpuff girls do programming.😂 The day is saved!

[@Quantumqbit]

Windows XP, Mac OS.... where is the Amiga Workbench?! 😛I still use various flavours of that on a daily basis....! Thanks for the video, perfect timing as I was just looking into this...and oddly enough, they recently fixed a stack overflow issue in Workbench!

[@Guishan_Lingyou]

When I learned about recursion it was in math, and the fact that it just kept on going was the point...infinite process represented with finite symbolic description.

[@DominikJaniec]

thank you. very interesting stuff! I find those layouts and transitions very enjoyably too - maybe I could wish to see letters a little bigger, I love reading code

[@MM-ts9jy]

I love Indian people and I owe them a lot as a programmer, but it's just nice to hear a different accent now and then. Also, nice production quality

[@wayneswildworld]

Beautifully executed visualization of a stack overflow. Simple and clear.

[@jorge.patino]

Ver que alguien tan joven tiene tanto dominio de la tecnología me da un poco de celos, pero ese estilo retro vintage me recuerda mis primeras interacciones con la tecnología en las que buscaba un experto que me entrenara, por lo que se me pasa los celos y me entra la nostalgia, jajaja, bendita juventud.

[@user-tc2ky6fg2o]

Your HEX calculator was so kind to inform us of the answer in decimal directly as well 😉

[@volsbit]

Loving your tutorials.

[@alphabitserial]

Oh my gosh I love what you've done with your hair!!

[@Pwnification]

Currently taking CS50 to start my programming journey and I really enjoyed this video. Luckily I'm far enough into the course to understand a good portion of what you were talking about! Thanks :)

[@ScottPuopolo]

Need to start a drinking game every time I hear 'actually'.

[@chyldstudios]

this is quality educational material while entertaining as well. it's a travesty you don't have more subs.

[@spiceyfrenchtoast9421]

Careful, it's hard to break the hypnotic trance.

[@dyslexicsoap7605]

so I'm guessing you did that asuka cosplay, realised "hold on, bangs are fucking lit" and then got bangs

[@ever.silva7]

Lain from Lain serial experiments... has reincarnated :-)

[@ant1fact]

Great video! Fun fact: at 9:20 the decimal value was automatically presented to you just underneath the hex result :)

[@c0p0n]

That was very well reasoned and explained.

[@LukeAvedon]

Amazing. How do you get the 90s mac OS vibe?

[@murtadha96]

Asuka is explaining a stack overflow :D

[@apex_prey]

Baby I will listen to and watch you read a car manual any day.

[@ThrillClips-io]

greetings from Lima, Peru

[@oneistar6661]

What a bright star! Very nice, thank you for doing this.

[@daljeetbhati8353]

Definately my one of fav vids from channel

[@xxge]

Really like the aesthetics here. It's sorta like bill nye but for comp sci. Crazy quality for a channel this size. You are definitely going to grow if you keep it up!

[@hyperxml]

I just came for the green light, stayed for the pointers 😮

[@ka1r0ww]

Great explanation and visual representation. I agree, the dark blue text was hard for me to read against the dark terminal/text editor. But other than that, great content. As someone who is "vintage," I love the retro vibe as well. I def. subscribed for more videos like this. Thanks!

[@kdog3908]

I'm exploring the idea of getting back into coding after about 30 years of never having looked at a line of it. Your videos are helping to poke (geddit?) memories loose from the rust that's accumulated over all that time. Thanks for posting and thanks for you!

[@jcKobeh]

Great diction, pronunciation, and voice recording quality. Fantastic job

[@SydneyApplebaum]

odd style, love it

[@dwsel]

Thank you I've learnt something new today. Also I appreciate visual progress bar showing filling up of the stack 👍

[@ganeshkale9665]

Can you share how you achieve good at your career in low level programming in security that would be so helpful 😃

[@mateusribcampos]

Thanks for an amazing explanation!

[@keithr6541]

Fantastic video! I've had to explain stack overflow in the past - you did a much better job. From now on I'll just send people here. I'd love to see a follow-on video about stack smashing and buffer overflow vulnerabilities, and how to write code to avoid them.

[@PyMike]

Your channel is 10/10, congrats from Italy, subscribed

[@scottriddell7893]

Great video. One tiny addition that might be informative would be to do an additional run without using the print statement. This would illustrate how much time screen IO adds to run time as well as show how fast the stack can fill from an unintended loop.

[@RiwenX]

Video: stack overflow Comments: simping overflow

[@soldierbirb]

I thought I would get tired of your way of talking (you look like a barbie) but actually, your voice and style is a little bit addictive lol. Good video!

[@kcsnipes]

i like this person's face, clicked cause the thumbnail but i dont code so i can't stay, wish you well on your youtube journey

[@squaredsquee7814]

This reminds me of Captain D. What a sick vibe.