3 ms·
That'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 Wi
by nnethercote 12y ago
That'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.