4 ms·
> but as time goes on, fragmentation results -- little bits of memory still get used even when a tab gets closed Don't you still have the same problem with mul
by MichaelBurge 9y ago
> but as time goes on, fragmentation results -- little bits of memory still get used even when a tab gets closed
Don't you still have the same problem with multiple processes, just moved to the kernel for them to deal with? It seems like if you kept everything in-process, you could use custom allocators and apply a sufficiently smart architecture so nothing stayed longer than necessary.
- korzun 9y agoThe custom allocators and smart architecture would add to the problem; not solve it.
- anyfoo 9y agoI think it's considered a pretty bad leak in the kernel if terminated processes leave unreclaimable memory behind.
- aidenn0 9y agoNot really because the kernel maps memory in paged-sized chunks. You do have variable page sizes on modern architectures but it's still just a very small number of block sizes for allocations. If they are non-contiguous in the kernel it is no barrier to making them contiguous in a process.