please wait
what happens after memory leaks ?
Jul 10, 2017 at 3:32pm
hi I just want to ask
what happens when I close a program with memory leak ?
is the memory returned ?
what happens when I close a program with memory leak ?
is the memory returned ?
Jul 10, 2017 at 4:04pm
Windows OS frees all memory allocated by the application.
Last edited on Jul 10, 2017 at 4:05pm
Jul 10, 2017 at 8:07pm
I think all modern OS return the memory when the program exits.
Memory leaks are a massive problem in programs that are left running for long periods, as they slowly but inevitably drive the machine (or at least that program) to a crash.
Memory leaks are a massive problem in programs that are left running for long periods, as they slowly but inevitably drive the machine (or at least that program) to a crash.
Jul 11, 2017 at 7:27am
Right, eventually you had to reboot the machines. Dos had this problem, but it had a ton of cool issues like allowing any program to edit any other programs(including the OS itself!) memory space! That will crash you on anything modern. Stuff from the mid 80s to early 90s. Around 1993 the internet was becoming mainstream and people were starting to think about hacks and security a bit, as well as stability and error recovery. To be fair, unix already discovered a lot of that stuff for corporate hardware, but it wasn't used on personal machines yet.
Last edited on Jul 11, 2017 at 7:29am
Jul 11, 2017 at 8:42am
jonnin: you're posts on computer/computing histories are always a treat to read!
Jul 11, 2017 at 12:51pm
The crappy OSs that jonnin talks about only apply to desktop operating systems. OS's that do proper memory management and isolate memory in each process have been around since the 1970's or earlier, but they were in the "big iron" mainframe computers of the day.
Virtual memory management, which is the key to both concepts, takes up transistors and must be fast. Both things mean that it was expensive in the 70's and 80's so it wasn't available. I think the 386 was the first x86 processor with memory management that was capable of isolating a user program from the OS and other programs. The 386 was released in 1985 and it took at least 10 years for Microsloth to really start using its features.
Virtual memory management, which is the key to both concepts, takes up transistors and must be fast. Both things mean that it was expensive in the 70's and 80's so it wasn't available. I think the 386 was the first x86 processor with memory management that was capable of isolating a user program from the OS and other programs. The 386 was released in 1985 and it took at least 10 years for Microsloth to really start using its features.
Last edited on Jul 11, 2017 at 12:51pm
Jul 11, 2017 at 1:58pm
anyway...is Microsloth supposed to be mocking microsoft ?
haha, Unix were much more expensive than windows after all (I think so)
haha, Unix were much more expensive than windows after all (I think so)
Jul 12, 2017 at 5:47am
haha
guess now their gates are gone they have to be more active
guess now their gates are gone they have to be more active
Topic archived. No new replies allowed.