Comment on This is why memory fragmentation is badparentComments−rwg15yAll of the physical RAM in the world doesn't mean a damned thing if you're a Win32 process limited to 2 GiB of user address space. Heap fragmentation is a very real problem there.−JoshTriplett15ySo don't run win32. :) We've had 64-bit processors for a while now, run a 64-bit OS and you have all the address space you might want.−silon15yLOL. Yesterday, I restarted firefox because it ate 13GB of virtual memory and started to get really unusable.−sid015yAnd even on 64-bit Windows, 32-bit Firefox will get the full 4 GB of address space.
Comments
All of the physical RAM in the world doesn't mean a damned thing if you're a Win32 process limited to 2 GiB of user address space. Heap fragmentation is a very real problem there.
So don't run win32. :) We've had 64-bit processors for a while now, run a 64-bit OS and you have all the address space you might want.
LOL. Yesterday, I restarted firefox because it ate 13GB of virtual memory and started to get really unusable.
And even on 64-bit Windows, 32-bit Firefox will get the full 4 GB of address space.