Allocating 4Gb+ of memory in x64 using Delphi XE2 Update 2: Unofficial fix for QC#100726 …
Posted by jpluimers on 2011/11/09
If you are creating x64 applications using Delphi XE2, have Update 2 installed, and are (potentially) allocating more than 4Gb of memory (QC report 100726), then you need the Unofficial fix for QC#100726, or use the latest version of FastMM (see below).
If you use Delphi XE2 (original release) or Update 1, then you don’t have problems in this scenario.
Thanks to FastMM author Pierre le Riche for providing this fix so quickly.
Note that the latest 4.x release of FastMM is now FastMM 4.99 and contains the same fix.
–jeroen
Via: Embarcadero Discussion Forums: Unofficial fix for QC#100726 ….
The Wiert Corner - irregular stream of stuff 
IL said
I’ve came acrross a little post about 64-bit Windows goodies
http://blogs.technet.com/b/askperf/archive/2011/09/02/why-run-64-bit-windows.aspx
It became much more useful with WOW64Menu which “allows using shell context menu of 32-bit applications on x64 editions of Windows. It adds “Show WOW64 Menu” command to context menu of objects on Desktop and in Windows Explorer. When choosing this command a new context menu including 32-bit applications will be shown.” http://www.gasanov.net/WOW64Menu.asp
IL said
Imagine, at the recent David I webinar on Delphi 64-bit development his example program allocated and freed 1000 times of 1024*1024 bytes successfully without any exception! But he said exception would have happened (the same as for 32-bit) if he tries to allocate more memory that his computer has. I’m not sure if he talked about physical memory only or virtual too.
Peter Turner said
Yeah, I saw this yesterday too, he must have allocated a little more than 4gb total. Is this patch for allocating (or loading into memory) more than 4GB at once? as in getmem(1024*1024*1024*4+1)
jpluimers said
I haven’t tried (no VM yet which has that much memory), but it is supposed to work.