summary refs log tree commit diff stats
path: root/lib/system
diff options
context:
space:
mode:
authorAraq <rumpf_a@web.de>2012-10-06 22:46:41 +0200
committerAraq <rumpf_a@web.de>2012-10-06 22:46:41 +0200
commit70fa5a6df0dfc3cbe1e046736651788a5fc490af (patch)
treeffeea5c53e61c040bc26c37ca9f54c432b8eb705 /lib/system
parenta85b5797184065f1b007fad93b2d27c91f2632e9 (diff)
downloadNim-70fa5a6df0dfc3cbe1e046736651788a5fc490af.tar.gz
attempt to fix #183
Diffstat (limited to 'lib/system')
-rwxr-xr-xlib/system/alloc.nim10
1 files changed, 7 insertions, 3 deletions
diff --git a/lib/system/alloc.nim b/lib/system/alloc.nim
index d6093c5b1..bcc70b853 100755
--- a/lib/system/alloc.nim
+++ b/lib/system/alloc.nim
@@ -17,8 +17,9 @@
 
 # some platforms have really weird unmap behaviour: unmap(blockStart, PageSize)
 # really frees the whole block. Happens for Linux/PowerPC for example. Amd64
-# and x86 are safe though:
-const weirdUnmap = not (defined(amd64) or defined(i386))
+# and x86 are safe though; Windows is special because MEM_RELEASE can only be
+# used with a size of 0:
+const weirdUnmap = not (defined(amd64) or defined(i386)) or defined(windows)
 
 when defined(posix): 
   const
@@ -75,7 +76,10 @@ elif defined(windows):
     # This means that the OS has some different view over how big the block is
     # that we want to free! So, we cannot reliably release the memory back to
     # Windows :-(. We have to live with MEM_DECOMMIT instead.
-    when reallyOsDealloc: VirtualFree(p, size, MEM_DECOMMIT)
+    # Well that used to be the case but MEM_DECOMMIT fragments the address
+    # space heavily, so we now treat Windows as a strange unmap target.
+    when reallyOsDealloc: VirtualFree(p, 0, MEM_RELEASE)
+    #VirtualFree(p, size, MEM_DECOMMIT)
 
 else: 
   {.error: "Port memory manager to your platform".}