I am very basically familiar with memory leaks in low level computer languages like C.
I can do hello world stuff, if I have the book with me. More complicated stuff with a book and examples. Things like that.
I have an idea for my WIP that will hinge on a memory leak situation, that is if my basic understanding is not totally incorrect. So to the question.
A memory leak occurs when a program claims a block of memory for some action and for some reason fails to release that block of memory when it is finished using it. So the next time it wants to perform that action it will claim a block of memory to do it.
Since it is not releasing these blocks when it is done using them, eventually the computer will run out of memory and bad things happen, like the computer slows or possibly even crashes.
To fix this problem, someone with access to the source code needs to go in and find the particular function that is not releasing the memory and fix that code.
Without access to the code, that can't be done.
If the system is rebooted, will that fix all the symptoms of the memory leak and return the system to smooth operation? At least until the memory is all used up again?
I'm pretty sure the answer is yes, I just want to make sure so I don't look like a total idiot if someone who knows their stuff reads the story.
I can do hello world stuff, if I have the book with me. More complicated stuff with a book and examples. Things like that.
I have an idea for my WIP that will hinge on a memory leak situation, that is if my basic understanding is not totally incorrect. So to the question.
A memory leak occurs when a program claims a block of memory for some action and for some reason fails to release that block of memory when it is finished using it. So the next time it wants to perform that action it will claim a block of memory to do it.
Since it is not releasing these blocks when it is done using them, eventually the computer will run out of memory and bad things happen, like the computer slows or possibly even crashes.
To fix this problem, someone with access to the source code needs to go in and find the particular function that is not releasing the memory and fix that code.
Without access to the code, that can't be done.
If the system is rebooted, will that fix all the symptoms of the memory leak and return the system to smooth operation? At least until the memory is all used up again?
I'm pretty sure the answer is yes, I just want to make sure so I don't look like a total idiot if someone who knows their stuff reads the story.