3 ms·
I was under the impression that modern kernels and memory allocators are clever enough to not initialise memory pages that have been allocated but not used yet,
by DrJokepu 12y ago
I was under the impression that modern kernels and memory allocators are clever enough to not initialise memory pages that have been allocated but not used yet, is that not the case? So unless you calloc() or memset() your newly allocated memory, overallocation won't really affect actual memory usage?
- nnethercote 12y agoThat's right. The untouched memory won't be committed, i.e. put into physical memory or swap. But it will take up address space, which can be a problem -- on Windows Firefox is a 32-bit process and running out of address space tends to happen more often than running out of physical memory, ironically enough.
- e12e 12y agoThat reminds me (as I now have windows 8.1 on one of my machines again) - does anyone know if there is a roadmap/plan for official 64bit builds of ff on win64?
- nnethercote 12y agoIt's being actively worked on. https://wiki.mozilla.org/Firefox/win64 https://wiki.mozilla.org/Firefox/win64 seems to be an up-to-date planning document.
- deleted 12y ago[deleted]
- throwawayaway 12y agoi think you will find memset 0 after most calls to malloc in the firefox code.
- deleted 12y ago[deleted]