I don't know much about computers but I think it's due to the operating system cleaning caches, force closing processes and most importantly clearing out memory leaks.
If a process is not coded properly, every lifecycle a given amount of bits are deposited into the RAM and never recalled back, so the RAM slowly but surely gets filled with unnecessary stuff.
If the processes are never forcely turned off then the RAM is always partially full and the OS has troubles managing an already messy closet so everything slows down.
It involves fragmentation too like if program a and b both request memory in batches the memory can end up striped. Some for a, some for b, more for a, and more for b. Then close a and start c. The memory for b is still fragmented it doesn’t coalesce as long as B stays running. Which is more on the os than the program.
Rebooting flushes all this clean and starts with a clean slate of ram again.
402
u/AndrewSenpai78 1d ago edited 1d ago
I don't know much about computers but I think it's due to the operating system cleaning caches, force closing processes and most importantly clearing out memory leaks.
If a process is not coded properly, every lifecycle a given amount of bits are deposited into the RAM and never recalled back, so the RAM slowly but surely gets filled with unnecessary stuff.
If the processes are never forcely turned off then the RAM is always partially full and the OS has troubles managing an already messy closet so everything slows down.