"Because if a manufacturer can't be bothered to make sure their software operates correctly, then they don't deserve your business." Words to live by. Now quit pre-ordering.
Windows (and other major OSs) keeps track of what chunk of memory each program uses, so when you close the program, the OS should clear all memory leaked by the program as well. So if you are heaving memory leakage with chrome for example, closing all tabs and the program can help to solve the problem from time to time.
+Sharpeye Reviews I've always thought "Dodge Ram" was an oxymoron. I really still can not believe they call their trucks that name. To me, it's the ultimate insult by Dodge toward the human population that buys their vehicles. Double you tee eff yo!
A quick correction: On most modern operating systems the OS keeps track of the memory being used too, allowing it to free up the memory when an application closes. So while a reboot of the system will always do the trick, you can generally just close and reopen the application to fix the leak.
Yeah closing fixes problem but os still doesnt know if that allocation will block anything on pc :P no owerload protection on mpdern kernels pcs yet ;p
@@ahmetmutlu348 my Opera internet browser is using 99% DISK and 63gb of my 64gb total only thing that solves it is if i do hard reboot by turning off the computer completely - waiting 5 minutes and then starting it up again but it only lasts for like maybe 40-50 minutes and then all of my 64gb ram gets used up again i cant stand this
@@TL.... probably some script is wrong either plugin or web page,or from virus, try using different browser or reinstalling it 64gb is lots of memory ;)
Wrong info at the beginning of this video (around 1:00). Even if a program fails to release memory areas WHILE it's running, esentially "forgetting" what chunks it has used, when you close it, the OS releases them because the OS keeps its own tabs on things like that. It does not know the details, it does not know that the application reserved area B and then forgot about it, but it does know that it has been asked to reserve A, B and C so when you exit, A B and C is marked as free. Short version: leaky app leaks while it's running. If you close it, the OS brings the mop and cleans that mess.
Linus, (or whoever from L. M. G read this) I really believe that a re-wording is necessary at 1:40 . When saying that the OS needs to use the hard drive space (Page file) instead of using the term "lead footed" I would say "extremely lethargic" or "molasses in January slow" or anything besides the current "lead footed" The reason I feel so strongly about this is that the term "lead footed" to 99% of people makes them picture a lead foot driver, meaning someone who drives really really fast because there foot is heavy on the gas pedal. And to someone who isn't very tech savvy and watches your videos to learn, they could definitely get the wrong idea from your choice of words.
1:01 When you actually _exit_ a program, i.e. terminate a process, all memory leaked within this process will be released. So, bad example. This also means that rebooting might be a somewhat drastic step to take if you have the option of just restarting the leaking software.
@@angelcaru Well to be fair Chrome was notorious for this issue back in the day...so makes sense why he used that as an example....but nonetheless a bad example as it was a niche case.
Generally, most memory leak happens in applications, modern OS kernel shouldn't leak. (It would be catastrophic) Many times, what happened is technically memory bloat, not memory leak. Which the application still keeps track of the allocated memory, but just not using them efficiently. (e.g. keeping cache that is useless in ram).
Or just watching a lot of short mp4 on windows 10... with basic apps that comes with Blood damn OS... 32gb of RAM? Nah. System process will eat that easly.
It should be noted, if a process is closed the kernel should release all memory assigned to that process page, so as long as the issue isn't in the operating system kernel itself, restarting the leaky program should free up the resources.
Any way we could get a 2023 longer version of this? Lately it seems many games are coming out with memory leaks and it'd be nice to see ya'll actually use tools and programs to help aid whatever the problem is. Hogwarts has had so many memory leaks it's crazy, and the Witcher 3 dx12 update introduced many new leaks there as well. When you still want to play the blasted game, but also wanna 'band-aid' patch for better performance, what do ya do?
This was a bit incorrect, memleaks are caused by only one thing, incorrect programming, which is asking for memory and forgetting to give it back when not needed. When an application simply hides instead of quitting (assuming quitting was the intended action), that is a stuck process and while it gives you some unusable memory, it does not mean it leaks. Quitting or killing an process causes the OS to free the memory associated to it, so a restart is unnecessary (unless the leak is in your drivers or kernel)
Another good thing to know is that closing the program that's leaking will free all the memory it was using (most moder operating systems will take care of that), so if you know ehat program is causing the issue that can temporarily solve the problem.
I can't believe I enjoy these videos! Linus I think you are quite funny but these are the things that I usually watch at 2:00am. When I have watched everything there is to watch! I find myself looking to see if there is a new Linus vid. I don't understand a lot of what you are explaining not computer savvy at all. We own a Mac and I know how to turn it on and that's about it. I guess I just wanted to say thanks for giving me something to look forward to
Each GDDR5 module is 32 bits, so a 384 bit graphics card with 6 GB of GDDR5 would have 12 memory modules (384/32=12). Since 1 GB=1024 MB, and 6 GB = 6144 MB, you can divide 6144 by 12 modules and you get 512 MB, so now you know that a 384 bit memory card such as the 980 ti has 12 GDDR5 memory modules with each modules capacity being 512 MB
***** quit nitpicking as you're not spreading any knowledge. For your information, ALL ram is labled as GB although "1 GB" of ram contains "1024 MB" of ram, go correct every ram manufacturer and labeler, not me. Just like how Windows shows a 1TB hard drive as "931 GB", it is easier to explain the subject by only explaining the topic rather than explaining unnecessary instances to only complicate the matter even further.
RobinHood East he gave a suggestion because he wanted to know how it worked, knowledge is not exclusively obtained by youtubers just because it's UA-cam. You're just angry because you have absolutely no clue about how it works even with an explanation
Another issue could be heat. Cpu's cycles will reduce to nothing if the temperature rises too high, giving that slow or locked up feel after several minutes. We just had this issue, a guy even swapped a motherboard, from working sister machine, but ambient temperature was above what the MB could cool down to. External fan was placed outside unit.
So if I have minecraft open, and it takes more and more ram overtime as it's opened (from 1GB to 2,3 and even 4GB of ram used, just it running in background) is it a memory leak or is it intendet to do this?
Some costume kernels for some android devices allow you to have a SWAP memory partition. There's an app that (with root and kernel support) will allow you to have 5gb. But keep mind that it will shorten the lifespan of your SD card and you can't do it on the internal storage because it well basically kill it. Also you need root to use an app to make a SWAP partition and a custom recovery to install a custom kernel that supports this.
To me, I thought Firefox was causing the memory leak but after intense digging and researching, it was Flash and plugin container that is causing the memory leak. Flash and plugin container don'r seem to behave together well.
you're incorrect; unless you're using shared memory, which is not common in typical apps, when an app exists all the resources are freed, whether you want it or not; the only thing you need to worry about and can affect you as a user using an app, is memory leaking while the app is running, depending on how much memory you're leaking that can have effects ranging from none, to the app crashing or exiting, to the the system performing slower because there's little memory left or reliance on virtual memory, to the whole system or arbitrary apps crashing or failing to run in weird ways, if your system is running out of memory and it cannot use virtual memory
This is so wrong, in all common modern operating systems once a program is closed, its memory is released. Memory leaks happens on the program's scope, worst case scenario just close the program and open it again (but it will keep happening). The indicator of a memory leak is almost always the program getting slower over time, and at some point crashing (Software aging), you never need to restart the whole computer. If you had took literally 5 minutes to search memory leak on Wikipedia or whatever you would have done a much better video, it's lame how you say the technical term system call in the middle of a nonsense discussion just to imply that you know what you're talking about. I'm not saying this was just wrong from a 'technical perspective', this was plain wrong and unhelpful in general, from an end user's perspective. It's impressive this video has 100k views, almost no dislikes and I haven't found a single comment stating that it is nonsensincal.
Yeah, Firefox is just as fast, it is owned by a non-profit organization that doesn't sell your information to everyone, or at least not as much of it, and it's most definitely more secure. People using Chrome just don't know how great Firefox is.
I thought this explanation was a bit confused. Usually a memory leak is when a program allocates heap memory, but forgets the address of that allocation, which then makes it impossible to de-allocate that memory. Over time, the program will request more & more address space from the host OS that it would not need if it was working properly. For example: char* x; x = new char[10]; // x now holds the address of 10 bytes allocated on the heap x = new char[10]; // oops! now it's impossible to free up the last allocation delete [] x; // we need to know what we allocated in order to deallocate
+vonkruel Yes, modern operating systems work rather well when it comes to freeing up memory allocated by a process that is being terminated. Way too much emphasis was put on that aspect.
"Did you try turning it off and turning it back on again?" This fixes so many problems, and yet I've found people are often resistant to this suggestion, as though it is some arduous task that takes hours. "Can't I do something else to fix it?"
This is not a huge problem for phones to be honest! When it comes to android, java (programming language) has garbage collection which does most of the memory cleaning stuff for you and I know even though iOS does not have garbage collection, it has a very good way of cleaning memory too. The problem when it comes to phones is that both methods are not REALLY good and in a lot of the cases it is upto the developers to clean the memory themselves. I'm pretty bad at this :(
Linus seems to have forgotten all about the "purge" or "sudo purge" command, which can be used in Terminal, or "%windir%\system32 undll32.exe advapi32.dll,ProcessIdleTasks" which can be used in Console to reset memory allocation, freeing up leaked memory
DeltaGaming purge will not fix the problem here. the purge command is used to flush the buffers, which has nothing to do with memory leaks. it even says on the man page of purge "it does not affect anonymous memory that has been allocated through malloc, vm_allocate, etc."
Not to long ago I was selected to try the WoW WoD beta. It crashed about an hour in and it even gave a system resource error (can't remember exactly what it said) but it was a memory leak. Pretty sure they fixed that issue before launch though.
Lance Lindle Lee I should be illegal to do this. A company should not be able to take money for a good or a service that is not in the marketplace yet. Apparently, enough people (or the right people) have not been burned enough by this yet.
Rickbearcat Nah, pre-paying is actually common place in business. There is such a thing called "unearned revenue" in accounting. The problem is than in those cases, the product is already complete. And, technically, when you shop online, you pay before you get the product. Again though, product is set in stone.
so I might be a little bit to late here, but a comma could really make the difference between people stopping with pre-ordering and people stopping with pre-ordering people.
I painfully learned that I had a defective monitor that would cause some form of endless loop of requests that would make my system progressively take more and more ram when it would attempt to put the monitors to sleep. Took me months to figure it out. No more sleepy time for the monitors. :(
Actually a lot of what you're talking about here is largely not as large a problem as you might think. Memory leaks rarely impact other processes unless the amount of memory being consumed by a singular process is significant. On a 32-bit process running on a 64-bit operating system, this limitation is hard enforced simply because 2^32 is a hard limit of about 4GB. If the application attempts to allocate more memory than that, the operating system will refuse to allow it -- how gracefully an application handles that will determine if it can continue running stable or crash. With a 64-bit application, the problem becomes a bit more significant because of how much more memory becomes available. But given the system will typically have *much* less memory than the OS can theoretically use -- I don't think we'll see 16 *exabytes* of RAM in anyone's computer in my lifetime, if ever -- the operating system is always going to be swapping blocks of memory out of RAM and onto storage in a process called "paging". With platter HDDs, paging can be quite painful to a process, which is why adding more memory to a system is the easiest way to improve overall system performance and stability. With SSDs, the performance penalty is significantly reduced and only becomes noticeable when you have an aging (read: increasingly slower) SSD or a large number of large processes running simultaneously. Paging has been part of Windows since Windows 3.1 (probably longer with NT) with a feature called "virtual memory", and is a major contributor to the ability of an operating system to multi-task effectively. Over time, the improvements to virtual memory have contributed to overall system speed and stability. And it also means that the more physical RAM you have, the less the OS needs to page into and out of RAM as it will only do so if physical RAM is running out. This is why one of the better ways to increase system performance if you run a lot of applications simultaneously is to have more physical RAM. So where do memory leaks come into play? You're correct when you say that memory leaks occur when an application requests a block of memory from the operating system and then later does not release it when it's done. That's the textbook definition of it, at least. Where this can be a problem is when a memory leak is repeated numerous times. If the leak occurs a lot in a short period of time, things can turn catastrophic quickly -- the application will crash or the OS entirely will crash out trying to keep up. Sluggishness, however, comes from the operating system trying to page memory blocks into and out of RAM that it thinks are in use, even when they're not. That's why the quickest way to keep a memory leak from impacting your system is to kill the process. Remember that the OS will do this automatically even if you have plenty of physical RAM to cover your running processes simply to keep the physical RAM free for processes that need it. Lesser-priority processes or processes that aren't using a lot of CPU time will have their memory blocks paged to primary storage until needed to keep the much faster physical RAM open. Processes allocate memory in heap blocks. But if an application needs 64 bytes of RAM for an operation, it will allocate significantly more than that -- typically on kilobyte multiples -- and then divvy that up as needed, requesting more only when needed. This is typically a lot more efficient than requesting numerous smaller blocks. And Windows manages and tracks all of these blocks and the processes that request them so it knows what it may later need to page into and out of RAM. The plus side of this comes when you kill the process: the OS will re-claim _all_ memory an application requested when it terminates whether it was released or not (note this was not true in non-NT versions of Windows -- meaning Windows ME and earlier). This absolutely does not mean an application can get wasteful with memory because of the paging I mentioned earlier. The more memory an application uses (which includes non-needed memory that hasn't been released), the more Windows has to manage and page into and out of RAM. Unfortunately memory management is a very poorly understood concept with lesser-experienced programmers (and even the experienced get it wrong on occasion), especially those who started learning programming in a language other than C/C++. So killing a process will typically end system sluggishness if a memory leak is what caused it. But a memory leak isn't the only kind of _resource_ leak that can impact a system. But again the design of the NT line of Windows operating systems (which includes XP and later) ensures that the impact of one process's wastefulness with system resources doesn't significantly impact every other process. But that can get overwhelmed if you have multiple processes being wasteful with memory and resources. A system restart helps too, but that should only be considered a last resort. Killing the wasteful process is typically all you need to do to free your system from a memory leak.
This actually happens a lot on my system, but it never gets to the point of 100% ram usage. Usually it's when I open a sh*ton of tabs in chrome, my fix is just a restart which works great, good to know it's an actual thing that can be diagnosed is somewhat normal.
You should've included information about the failure/lack of garbage collectors within different coding languages. C++, for the most (if not all) the cases, need its own garbage collector to be programmed within the program itself while C# and Java usually have their own, but it's not the best or recommended. When garbage collectors fail (or don't exist), the program doesn't de-allocate the memory it was using to free up space on the computer's RAM.
MrMightyGnome well I think that is more in the case of memory management in general rather than a garbage collector. A garbage collector is actually very specific, in that it is a automatic process which clears memory for you. You can have very well written code, that has no garbage collector, simply by managing your own memory. Its actually very useful when performance is a high priority, since there is no need an interrupt of the main thread to process the garbage.
Yeah of course, I don't mean they should make this whole thing about garbage collectors. I just merely meant that he should have just -mentioned- something about it at least. I'm not saying all programs need a garbage collector either. :)
There‘s something does not seem to be correct. The operating system knows which program had which part of memory allocated. If the memory leaked at the program run time, the system cannot deallocate that chunk of memory of course, because it doesn't know if the memory has to be used anymore. But when a process terminates, the operating system is going to deallocate all of its memory. If this didn't happen, then it is a bug in the opersting system virtual memory mechanism.
I ran into a Trojan that would constantly run background web browser based links that hogged up all of my system memory. I ended up doing a fresh install of Windows to remedy the problem.
One thing that usually demands a LOT of RAM is svchost.exe whenever windows is trying to download updates. Sometimes it brings the system to a crawl. Strangely enough, even after disconnecting the system from any internet connections, it will still keep trying to download it it for quite a while.
Win10 users with Killer Networks stuff, or at least the E2200 will have memory leaks filling up nonpaged memory. this is memory so important that it can't be put in the pagefile. Or it's supposed to be but in reality it's the NDU.sys file causing it. This monitors network usage and basically only controls the usage alerts for capped connections. Disable it and nonpaged memory won't increase to massive levels anymore.
Doesn't memory a program uses on the heap get freed by modern operating systems when the program is fully terminated? I'm a programmer working on making games, and when I was concerned about the way I was handling crashes I looked it up and that is what seemed to be the unanimous explanation. It coincides with my experience, too, since older versions of Firefox had terrible memory leakage problems, and just restarting the browser would at least seem to fix it.
it should even if u alocate memory and u make u program don't use it, after a few minutes the os release it (atleast happens on w10) i can see a programm that don't close a process or have always a background process on all the time having this issue, but usually it should never require a os restart just the program itself. OS today are very good to release memory after a aplication closes so that case of the memory becoming still in use after a program closes must be a very special case, or the program did not really close and was still on the background in some way.
The biggest problem I ever had was Firefox believe it or not, I switched to Brave. Firefox would have ram spikes that would eat the Vram in Windows 10, this would then expand then crash the Paging file. This would eventually create an instability in Windows and crash every file I would open after, I needed to restart when this would happen to reset it back to normal. I tested my Ram and no errors came up so I finally narrowed it down to when I had Firefox open in UA-cam, even if it was just open and not playing it would sometimes have a Ram surge, and I saw it in real time once with the usage monitor. I have not had a problem in days now that I switched over. This all started for me on and off in December, I wonder if aspects of it had anything to do with the phasing out of Flash player and how that coding reacted to Firefox and Windows 10. All I know is that someone dropped the ball big time with Firefox in the last 3 updates and it forced me to move on to what seems to be a more stable browser.
I hate to say, you shouldn't ditch software/games if they don't properly unload memory like saints. Many game engines (great example: Java) can be extremely prone to triggering memory leaks from relatively tiny issues, or more often, the memory leak rates are very very slow, and make take within the hours-type timeframe to make an impact on performance. I don't think one simply finds games or processes that consume memory at such a staggering, sloppy pace that they are forced to ditch them, and I've played some poorly optimized crap before.
This is one reason why open source code is important. Sure you might not be able to fix a memory leak but some people do know how to and they will probably fix it for you if you complain enough.
IMO, I think you should take it easy on the stock images on Techquickie. Can't focus half the time on what you're saying cuz of the distracting pics flying everywhere. Maybe do some infographics that actually make sense and help explain your points as fast as possible (which is the whole purpose).
photoshop cs2 has some awesome memory leakage, if left open for 10 minutes it will use 3.9gb of my ram (8gb total) and then it will freeze, unable to do anything, even save or close (have to go to task manager and close it there, hoping I saved picture before)
Can you explain computers? In General? like what different parts do, and simple things about them? for other people of course, but I wish it was made in the past...
Is microsoft paint supposed to use 6.7Gb of ram?
Flamealchamist Nope. Paint on my computer uses about 7 mb.
503technics did you really just responded seriously to that?
Flamealchamist Yes
Flamealchamist its supposed to use 9.1TB ram.
is it 6.7 Gigabit or 6.7 Gigabyte
Jonathan Ferrante *did* you really just *answered* with double past tense?
"Because if a manufacturer can't be bothered to make sure their software operates correctly, then they don't deserve your business."
Words to live by. Now quit pre-ordering.
agree
except for Cyberpunk 2077 by CD Projekt Red
@@LordVollmilch the only game company I'd fully trust atm
@@LordVollmilch ohnononoo december 10th pepelaugh
@@onesevenninewest This comment didn't age very well...
@@LordVollmilch
I was expecting a comment like this
Not disappointed
I think got a memory leak. My heead is leaking red liquid, and my my memory seem to to be getting worse and worse and worse and worse and worse.
I see what you did there...
asdf30111 do not get. i am potato
asdf30111 Only really worry if it starts leaking grey-matter!
Fallenex e i tried, it does not work
Fallenex e
That will just make you go blind! Lol!
Windows (and other major OSs) keeps track of what chunk of memory each program uses, so when you close the program, the OS should clear all memory leaked by the program as well. So if you are heaving memory leakage with chrome for example, closing all tabs and the program can help to solve the problem from time to time.
I was at like 98% ram everytime I booted up my computer... Turned off the power supply and BOOM it was fine.
+DerpMans Derpyskin is it cos you had like 1gb of ram
Tony's tech I have 8gb
orr k
+DerpMans Derpyskin wow 3:03 true theory ?
That isn't Memory Leak if you're at 98% when you boot up your computer.
The car of the future runs on ram, never saw that coming. 0:00
Sharpeye Reviews ...& it's loaded via the dipstick!!!
Sharpeye Reviews a lamborghini exclusive feature.
Sharpeye Reviews Yeah it's a Dodge Ram......
That's not The Ram! Where are the horns on top
+Sharpeye Reviews I've always thought "Dodge Ram" was an oxymoron. I really still can not believe they call their trucks that name. To me, it's the ultimate insult by Dodge toward the human population that buys their vehicles. Double you tee eff yo!
lol. Was that a picture of TB?
Yes
SangoProductions21 ding ding ding
SangoProductions21 never knew you could make a picture of a terabyte
0M9H4X you total biscuit....
SangoProductions21 Took me a few seconds to recognize him and read the pic. That one was golden, had a good laugh. :D
A quick correction: On most modern operating systems the OS keeps track of the memory being used too, allowing it to free up the memory when an application closes. So while a reboot of the system will always do the trick, you can generally just close and reopen the application to fix the leak.
Yeah closing fixes problem but os still doesnt know if that allocation will block anything on pc :P no owerload protection on mpdern kernels pcs yet ;p
@@ahmetmutlu348 my Opera internet browser is using 99% DISK and 63gb of my 64gb total
only thing that solves it is if i do hard reboot by turning off the computer completely - waiting 5 minutes and then starting it up again
but it only lasts for like maybe 40-50 minutes and then all of my 64gb ram gets used up again
i cant stand this
@@TL.... probably some script is wrong either plugin or web page,or from virus, try using different browser or reinstalling it 64gb is lots of memory ;)
@@TL.... haha you dont have to wait 5 minutes. you dont even have to shut down. restart is enough.
@@TL.... opera is trash use firefox and u dont need to wait 5 minutes restart is enough
"Google task manager" 2:33 , Microsoft renamed the task manager?
Mihail Georgescu No, he said "Good old Task Manager"
Mihail Georgescu I heard the same thing the first time, I had to rewind to check again.
Ohh shit my bad Linus . I will whip myself now.
Mihail Georgescu Well I just spent 10 minutes googling for that wonderful task manager, that looked exactly like the MS one. Silly me.
I thought he said "Google Task Manager" the first time as well. I had to jump back 5 seconds.
"Did you try turning it off, then turning it back off again?" *Dun-dun-dun!*
X'D PRICELESS!
Wrong info at the beginning of this video (around 1:00). Even if a program fails to release memory areas WHILE it's running, esentially "forgetting" what chunks it has used, when you close it, the OS releases them because the OS keeps its own tabs on things like that. It does not know the details, it does not know that the application reserved area B and then forgot about it, but it does know that it has been asked to reserve A, B and C so when you exit, A B and C is marked as free.
Short version: leaky app leaks while it's running. If you close it, the OS brings the mop and cleans that mess.
you also can just close whatever's leaking to free up the resources instead of restarting (unless it's a system process or the kernel of course)
Linus, (or whoever from L. M. G read this) I really believe that a re-wording is necessary at 1:40 . When saying that the OS needs to use the hard drive space (Page file) instead of using the term "lead footed" I would say "extremely lethargic" or "molasses in January slow" or anything besides the current "lead footed"
The reason I feel so strongly about this is that the term "lead footed" to 99% of people makes them picture a lead foot driver, meaning someone who drives really really fast because there foot is heavy on the gas pedal. And to someone who isn't very tech savvy and watches your videos to learn, they could definitely get the wrong idea from your choice of words.
game freak devs should watch this
The TB cameo was perfect.
Sometimes I watch these knowing full well what the thing is but it's nice to make sure.
What is that sounds effect called that's used when Linus told the corny joke? I can't quite find it.
It's at 3:06
Reading rainbow
Darude-sandstorm
Mat Mabee i like the sound though
ua-cam.com/video/QytfpesdBfA/v-deo.html
1:01 When you actually _exit_ a program, i.e. terminate a process, all memory leaked within this process will be released. So, bad example. This also means that rebooting might be a somewhat drastic step to take if you have the option of just restarting the leaking software.
Yeah, restarting only really helps for driver memory leaks
@@angelcaru Well to be fair Chrome was notorious for this issue back in the day...so makes sense why he used that as an example....but nonetheless a bad example as it was a niche case.
Generally, most memory leak happens in applications, modern OS kernel shouldn't leak. (It would be catastrophic)
Many times, what happened is technically memory bloat, not memory leak. Which the application still keeps track of the allocated memory, but just not using them efficiently.
(e.g. keeping cache that is useless in ram).
Or just watching a lot of short mp4 on windows 10... with basic apps that comes with Blood damn OS... 32gb of RAM? Nah. System process will eat that easly.
You can always download more RAM if you need it, No seriously dont do that. LOL
Nice TB reference there ;)
ZeroTheHero I don't remember him talking about TeraBytes (TB), that is a lot of ram though.
***** I thought that was Tuberculosis xD
ZeroTheHero Download more dedotated wam
***** I will defer you to Linus' quip: ". . . And the OS is forced to use lead-footed hard drive space. . ." Where 'lead-footed' means slow-as-hell.
ZeroTheHero www.downloadmoreram.com
It should be noted, if a process is closed the kernel should release all memory assigned to that process page, so as long as the issue isn't in the operating system kernel itself, restarting the leaky program should free up the resources.
Any way we could get a 2023 longer version of this? Lately it seems many games are coming out with memory leaks and it'd be nice to see ya'll actually use tools and programs to help aid whatever the problem is. Hogwarts has had so many memory leaks it's crazy, and the Witcher 3 dx12 update introduced many new leaks there as well. When you still want to play the blasted game, but also wanna 'band-aid' patch for better performance, what do ya do?
Just download more ram and you'll be fine
nah.. not enough, download nvidia gtx-1080 is enough for me
@@LandonMakesCrap r/woosh
I think you would be better off downloading new CPU ram and Gpu. Might as well download liquid cooling as well. That will help.
This was a bit incorrect, memleaks are caused by only one thing, incorrect programming, which is asking for memory and forgetting to give it back when not needed. When an application simply hides instead of quitting (assuming quitting was the intended action), that is a stuck process and while it gives you some unusable memory, it does not mean it leaks. Quitting or killing an process causes the OS to free the memory associated to it, so a restart is unnecessary (unless the leak is in your drivers or kernel)
Another good thing to know is that closing the program that's leaking will free all the memory it was using (most moder operating systems will take care of that), so if you know ehat program is causing the issue that can temporarily solve the problem.
I can't believe I enjoy these videos! Linus I think you are quite funny but these are the things that I usually watch at 2:00am. When I have watched everything there is to watch! I find myself looking to see if there is a new Linus vid. I don't understand a lot of what you are explaining not computer savvy at all. We own a Mac and I know how to turn it on and that's about it. I guess I just wanted to say thanks for giving me something to look forward to
If you have free time buy a computer, I'm sure you'll have a lot of fun with it.
I appreciate the John Bain in this video
RIP
Thanks for this video! Memory leaks are talked about sometimes in Minecraft modding, but I didn’t know what that was
I would like to see the 64, 128, 256bit video cards explained.
Difference between amount of bits that can be transferred at a time.
Each GDDR5 module is 32 bits, so a 384 bit graphics card with 6 GB of GDDR5 would have 12 memory modules (384/32=12). Since 1 GB=1024 MB, and 6 GB = 6144 MB, you can divide 6144 by 12 modules and you get 512 MB, so now you know that a 384 bit memory card such as the 980 ti has 12 GDDR5 memory modules with each modules capacity being 512 MB
***** quit nitpicking as you're not spreading any knowledge. For your information, ALL ram is labled as GB although "1 GB" of ram contains "1024 MB" of ram, go correct every ram manufacturer and labeler, not me. Just like how Windows shows a 1TB hard drive as "931 GB", it is easier to explain the subject by only explaining the topic rather than explaining unnecessary instances to only complicate the matter even further.
Fearbeavis smith why are YOU guys replying? if he wanted other people to reply he would go into a forum or ask yahoo. this is a SUGGESTION
RobinHood East he gave a suggestion because he wanted to know how it worked, knowledge is not exclusively obtained by youtubers just because it's UA-cam. You're just angry because you have absolutely no clue about how it works even with an explanation
"Program or game"? Linus, video games _are_ programs. (Will you use a text card right there at 3:23 saying "I just meant 'program' "?)
Silly Linus that car in the beginning wasn't a Ram.
Honda civics have ram
Dodge ram
a car can ram get it in to a wall
So
Motherboard Chipsets as fast as possible (X99, B75, H81etc)
Pin locations there I did it for him
Rushikesh Badbade alreay done son
found it, thanks
How about in rendering? VRAM vs Physical Memory? pls discuss it +Techquickie
Another issue could be heat. Cpu's cycles will reduce to nothing if the temperature rises too high, giving that slow or locked up feel after several minutes. We just had this issue, a guy even swapped a motherboard, from working sister machine, but ambient temperature was above what the MB could cool down to. External fan was placed outside unit.
You are the best worlds technology enthusiast spoke person Linus !
3:03 the best part
So if I have minecraft open, and it takes more and more ram overtime as it's opened (from 1GB to 2,3 and even 4GB of ram used, just it running in background) is it a memory leak or is it intendet to do this?
Some costume kernels for some android devices allow you to have a SWAP memory partition. There's an app that (with root and kernel support) will allow you to have 5gb. But keep mind that it will shorten the lifespan of your SD card and you can't do it on the internal storage because it well basically kill it. Also you need root to use an app to make a SWAP partition and a custom recovery to install a custom kernel that supports this.
To me, I thought Firefox was causing the memory leak but after intense digging and researching, it was Flash and plugin container that is causing the memory leak. Flash and plugin container don'r seem to behave together well.
Looks like a nice format good instructions and clear explanations of what the issues is. I like it! Deffo subscribing!
you're incorrect; unless you're using shared memory, which is not common in typical apps, when an app exists all the resources are freed, whether you want it or not; the only thing you need to worry about and can affect you as a user using an app, is memory leaking while the app is running, depending on how much memory you're leaking that can have effects ranging from none, to the app crashing or exiting, to the the system performing slower because there's little memory left or reliance on virtual memory, to the whole system or arbitrary apps crashing or failing to run in weird ways, if your system is running out of memory and it cannot use virtual memory
This is so wrong, in all common modern operating systems once a program is closed, its memory is released.
Memory leaks happens on the program's scope, worst case scenario just close the program and open it again (but it will keep happening).
The indicator of a memory leak is almost always the program getting slower over time, and at some point crashing (Software aging), you never need to restart the whole computer.
If you had took literally 5 minutes to search memory leak on Wikipedia or whatever you would have done a much better video, it's lame how you say the technical term system call in the middle of a nonsense discussion just to imply that you know what you're talking about.
I'm not saying this was just wrong from a 'technical perspective', this was plain wrong and unhelpful in general, from an end user's perspective.
It's impressive this video has 100k views, almost no dislikes and I haven't found a single comment stating that it is nonsensincal.
Chrome... I'm looking at you, buddy.
Yeah, Firefox is just as fast, it is owned by a non-profit organization that doesn't sell your information to everyone, or at least not as much of it, and it's most definitely more secure. People using Chrome just don't know how great Firefox is.
3:03 IT Department at your service
I love how he says "Dislike the video if you thought it sucked" lol.
Rule of thumb: A program's allocated memory is reclaimed by the OS upon (clean/dirty) exit. That, if the system is not compromised.
Oh man, that totalbiscuit stockphoto was perfect!
2:08 nice knife, FN stat?
Oh, does the toaster have ToastTrack(TM) technology?
That jab at pre-orders was literally #savageasfuck
User: how much memory do you need?
Adobe products: yes.
I thought this explanation was a bit confused. Usually a memory leak is when a program allocates heap memory, but forgets the address of that allocation, which then makes it impossible to de-allocate that memory. Over time, the program will request more & more address space from the host OS that it would not need if it was working properly.
For example:
char* x;
x = new char[10]; // x now holds the address of 10 bytes allocated on the heap
x = new char[10]; // oops! now it's impossible to free up the last allocation
delete [] x; // we need to know what we allocated in order to deallocate
+vonkruel Yes, modern operating systems work rather well when it comes to freeing up memory allocated by a process that is being terminated. Way too much emphasis was put on that aspect.
wow linus's tech tips sure are good
"Did you try turning it off and turning it back on again?" This fixes so many problems, and yet I've found people are often resistant to this suggestion, as though it is some arduous task that takes hours. "Can't I do something else to fix it?"
look really close to the left at 2:46 you can see his fingers get cut off
Where is the sound from that they use at 3:06 ?
you guys should definitely do a "Physical Based Rendering as Fast as Possible" since that term was thrown around so much this year at E3
This is not a huge problem for phones to be honest! When it comes to android, java (programming language) has garbage collection which does most of the memory cleaning stuff for you and I know even though iOS does not have garbage collection, it has a very good way of cleaning memory too. The problem when it comes to phones is that both methods are not REALLY good and in a lot of the cases it is upto the developers to clean the memory themselves. I'm pretty bad at this :(
3:05 what was that noise, I've heard it before
Linus seems to have forgotten all about the "purge" or "sudo purge" command, which can be used in Terminal, or "%windir%\system32
undll32.exe advapi32.dll,ProcessIdleTasks" which can be used in Console to reset memory allocation, freeing up leaked memory
You can also manually clear RAM in the "Processes" tab of Windows Task Manager.
DeltaGaming purge will not fix the problem here. the purge command is used to flush the buffers, which has nothing to do with memory leaks. it even says on the man page of purge "it does not affect anonymous memory that has been allocated through malloc, vm_allocate, etc."
Not to long ago I was selected to try the WoW WoD beta. It crashed about an hour in and it even gave a system resource error (can't remember exactly what it said) but it was a memory leak. Pretty sure they fixed that issue before launch though.
I liked just for you showing Totalbiscuit. Stop preordering people!
Yes, it incentiveses devs to not care anymore 'cause they already have the movey
Lance Lindle Lee I should be illegal to do this. A company should not be able to take money for a good or a service that is not in the marketplace yet. Apparently, enough people (or the right people) have not been burned enough by this yet.
Rickbearcat Nah, pre-paying is actually common place in business. There is such a thing called "unearned revenue" in accounting. The problem is than in those cases, the product is already complete.
And, technically, when you shop online, you pay before you get the product. Again though, product is set in stone.
ME too hahahahah.
When will people stop pre ordering!
so I might be a little bit to late here, but a comma could really make the difference between people stopping with pre-ordering and people stopping with pre-ordering people.
Linus, the only one who checks your car and tells you what's wrong with your PC.
I painfully learned that I had a defective monitor that would cause some form of endless loop of requests that would make my system progressively take more and more ram when it would attempt to put the monitors to sleep. Took me months to figure it out. No more sleepy time for the monitors. :(
certain games like Prototype 2 never had the RAM leakage issue fixed as the developers were laid off after releasing the game...
Actually a lot of what you're talking about here is largely not as large a problem as you might think. Memory leaks rarely impact other processes unless the amount of memory being consumed by a singular process is significant. On a 32-bit process running on a 64-bit operating system, this limitation is hard enforced simply because 2^32 is a hard limit of about 4GB. If the application attempts to allocate more memory than that, the operating system will refuse to allow it -- how gracefully an application handles that will determine if it can continue running stable or crash. With a 64-bit application, the problem becomes a bit more significant because of how much more memory becomes available.
But given the system will typically have *much* less memory than the OS can theoretically use -- I don't think we'll see 16 *exabytes* of RAM in anyone's computer in my lifetime, if ever -- the operating system is always going to be swapping blocks of memory out of RAM and onto storage in a process called "paging". With platter HDDs, paging can be quite painful to a process, which is why adding more memory to a system is the easiest way to improve overall system performance and stability. With SSDs, the performance penalty is significantly reduced and only becomes noticeable when you have an aging (read: increasingly slower) SSD or a large number of large processes running simultaneously.
Paging has been part of Windows since Windows 3.1 (probably longer with NT) with a feature called "virtual memory", and is a major contributor to the ability of an operating system to multi-task effectively. Over time, the improvements to virtual memory have contributed to overall system speed and stability. And it also means that the more physical RAM you have, the less the OS needs to page into and out of RAM as it will only do so if physical RAM is running out. This is why one of the better ways to increase system performance if you run a lot of applications simultaneously is to have more physical RAM.
So where do memory leaks come into play? You're correct when you say that memory leaks occur when an application requests a block of memory from the operating system and then later does not release it when it's done. That's the textbook definition of it, at least. Where this can be a problem is when a memory leak is repeated numerous times. If the leak occurs a lot in a short period of time, things can turn catastrophic quickly -- the application will crash or the OS entirely will crash out trying to keep up.
Sluggishness, however, comes from the operating system trying to page memory blocks into and out of RAM that it thinks are in use, even when they're not. That's why the quickest way to keep a memory leak from impacting your system is to kill the process. Remember that the OS will do this automatically even if you have plenty of physical RAM to cover your running processes simply to keep the physical RAM free for processes that need it. Lesser-priority processes or processes that aren't using a lot of CPU time will have their memory blocks paged to primary storage until needed to keep the much faster physical RAM open.
Processes allocate memory in heap blocks. But if an application needs 64 bytes of RAM for an operation, it will allocate significantly more than that -- typically on kilobyte multiples -- and then divvy that up as needed, requesting more only when needed. This is typically a lot more efficient than requesting numerous smaller blocks. And Windows manages and tracks all of these blocks and the processes that request them so it knows what it may later need to page into and out of RAM.
The plus side of this comes when you kill the process: the OS will re-claim _all_ memory an application requested when it terminates whether it was released or not (note this was not true in non-NT versions of Windows -- meaning Windows ME and earlier). This absolutely does not mean an application can get wasteful with memory because of the paging I mentioned earlier. The more memory an application uses (which includes non-needed memory that hasn't been released), the more Windows has to manage and page into and out of RAM. Unfortunately memory management is a very poorly understood concept with lesser-experienced programmers (and even the experienced get it wrong on occasion), especially those who started learning programming in a language other than C/C++.
So killing a process will typically end system sluggishness if a memory leak is what caused it. But a memory leak isn't the only kind of _resource_ leak that can impact a system. But again the design of the NT line of Windows operating systems (which includes XP and later) ensures that the impact of one process's wastefulness with system resources doesn't significantly impact every other process. But that can get overwhelmed if you have multiple processes being wasteful with memory and resources. A system restart helps too, but that should only be considered a last resort. Killing the wasteful process is typically all you need to do to free your system from a memory leak.
ya, solidworks leaks like crazy. a few hours of cad and I get these scary low resource warnings just from opening a new part.
that TotalBiscuit pic. perfection
In CS terms, it's when you malloc(reserve) memory without freeing it
This actually happens a lot on my system, but it never gets to the point of 100% ram usage. Usually it's when I open a sh*ton of tabs in chrome, my fix is just a restart which works great, good to know it's an actual thing that can be diagnosed is somewhat normal.
You should've included information about the failure/lack of garbage collectors within different coding languages. C++, for the most (if not all) the cases, need its own garbage collector to be programmed within the program itself while C# and Java usually have their own, but it's not the best or recommended. When garbage collectors fail (or don't exist), the program doesn't de-allocate the memory it was using to free up space on the computer's RAM.
MrMightyGnome well I think that is more in the case of memory management in general rather than a garbage collector. A garbage collector is actually very specific, in that it is a automatic process which clears memory for you.
You can have very well written code, that has no garbage collector, simply by managing your own memory. Its actually very useful when performance is a high priority, since there is no need an interrupt of the main thread to process the garbage.
Yeah of course, I don't mean they should make this whole thing about garbage collectors. I just merely meant that he should have just -mentioned- something about it at least. I'm not saying all programs need a garbage collector either. :)
that sound bite and face lol, killed it
So what do you do if you have say.... a RAID card that causes memory leaks after large read/write tasks?
There‘s something does not seem to be correct. The operating system knows which program had which part of memory allocated. If the memory leaked at the program run time, the system cannot deallocate that chunk of memory of course, because it doesn't know if the memory has to be used anymore. But when a process terminates, the operating system is going to deallocate all of its memory. If this didn't happen, then it is a bug in the opersting system virtual memory mechanism.
The graph function in a very old version of Word for Windows had a memory leak. You'd go in and out of graph 3-4 times and then the PC would crash.
I ran into a Trojan that would constantly run background web browser based links that hogged up all of my system memory. I ended up doing a fresh install of Windows to remedy the problem.
now you guys are giving an advertisement for over an minute.whereas we skip the ad to watch your video and still you are showing another ad in it.
I can't seem to find the terabyte joke in the video everyone is talking about....
/s
One thing that usually demands a LOT of RAM is svchost.exe whenever windows is trying to download updates. Sometimes it brings the system to a crawl. Strangely enough, even after disconnecting the system from any internet connections, it will still keep trying to download it it for quite a while.
that svchost.exe might be infected normally it doesn't behave that way
Win10 users with Killer Networks stuff, or at least the E2200 will have memory leaks filling up nonpaged memory. this is memory so important that it can't be put in the pagefile. Or it's supposed to be but in reality it's the NDU.sys file causing it. This monitors network usage and basically only controls the usage alerts for capped connections. Disable it and nonpaged memory won't increase to massive levels anymore.
Which can look like code that makes variables which are not recycled or not flushed but kept alive somehow
Doesn't memory a program uses on the heap get freed by modern operating systems when the program is fully terminated? I'm a programmer working on making games, and when I was concerned about the way I was handling crashes I looked it up and that is what seemed to be the unanimous explanation. It coincides with my experience, too, since older versions of Firefox had terrible memory leakage problems, and just restarting the browser would at least seem to fix it.
it should even if u alocate memory and u make u program don't use it, after a few minutes the os release it (atleast happens on w10) i can see a programm that don't close a process or have always a background process on all the time having this issue, but usually it should never require a os restart just the program itself. OS today are very good to release memory after a aplication closes so that case of the memory becoming still in use after a program closes must be a very special case, or the program did not really close and was still on the background in some way.
The biggest problem I ever had was Firefox believe it or not, I switched to Brave. Firefox would have ram spikes that would eat the Vram in Windows 10, this would then expand then crash the Paging file. This would eventually create an instability in Windows and crash every file I would open after, I needed to restart when this would happen to reset it back to normal. I tested my Ram and no errors came up so I finally narrowed it down to when I had Firefox open in UA-cam, even if it was just open and not playing it would sometimes have a Ram surge, and I saw it in real time once with the usage monitor. I have not had a problem in days now that I switched over. This all started for me on and off in December, I wonder if aspects of it had anything to do with the phasing out of Flash player and how that coding reacted to Firefox and Windows 10. All I know is that someone dropped the ball big time with Firefox in the last 3 updates and it forced me to move on to what seems to be a more stable browser.
thank you for explaining that to me ... now how do I fix a gedit memory leak on Mint Linux?
1:49 Nice Tim And Eric Reference
I love this enthusiasm
Sometimes the perfect sound byte can make a scene. "Did you try turning it off and turning it back on again?" Da-duh-dun! I LOL'd so hard.
I hate to say, you shouldn't ditch software/games if they don't properly unload memory like saints. Many game engines (great example: Java) can be extremely prone to triggering memory leaks from relatively tiny issues, or more often, the memory leak rates are very very slow, and make take within the hours-type timeframe to make an impact on performance.
I don't think one simply finds games or processes that consume memory at such a staggering, sloppy pace that they are forced to ditch them, and I've played some poorly optimized crap before.
Is the doot doot doot at 3:06 from something else?
This is one reason why open source code is important. Sure you might not be able to fix a memory leak but some people do know how to and they will probably fix it for you if you complain enough.
Skype. Skype does this 8GB of RAM leakage for me with no solution in sight.
Nana7suYoru Skoop skoops up all your memory.
Nana7suYoru Runs all the time on my PC. Using about 144MB of ram atm. But then again, I have its ads blocked.
soulshot96 172mB here with adds not blocked. 12 hours uptime. op has underlying issue
EZOVERDOSE Doesn't surprise me, most people haven't the faintest idea how to keep their computer 'clean' and in good working order.
Its because you use skype ya nub
Is memory leakage solely caused by bad coding, or can old/damaged physical components on RAM cause it as well?
RIP TotalBiscuit.
dat TB refrence made my day :D
3:13 Instantly feels all the anger of video watchers
IMO, I think you should take it easy on the stock images on Techquickie. Can't focus half the time on what you're saying cuz of the distracting pics flying everywhere. Maybe do some infographics that actually make sense and help explain your points as fast as possible (which is the whole purpose).
3:31 What was THAT in the background?
photoshop cs2 has some awesome memory leakage, if left open for 10 minutes it will use 3.9gb of my ram (8gb total) and then it will freeze, unable to do anything, even save or close (have to go to task manager and close it there, hoping I saved picture before)
Linus hasnt changed in 3 years. Crazy to think 2015 was 3 years ago now.
2021: Learning Data Structures from Linus
Can you explain computers? In General? like what different parts do, and simple things about them? for other people of course, but I wish it was made in the past...
Confession: I watch these videos just for the ads at the end :3