[python-win32] RAM with Pywin32 on Windows-64

[Massa, Harald Armin]

Michael,

I did a quick google for available memory per process win32 on win64

http://www.google.de/search?q=available+memory+per+process+win32+on+win64&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a

and my first hit is:

http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx

there I read:

User-mode virtual address space for each 32-bit process

limit in 32-bit windows:
2 GB
Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT

limit in 64-bit windows:
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)
4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set

so, I guess your IMAGE_FILE_LARGE_ADDRESS_AWARE ist set on your 64bit
machine, which explains the 4Gig.

Best wishes,

Harald




On Sun, Aug 8, 2010 at 22:07, Michel Claveau <mc at mclaveau.com> wrote:
> Hi, all!
>
> I have a script, in Pywin32, with a leak memory.
> OK, it is my bug (a problem for me, not for you).
>
> But I seen a bizar trick...
>
> When I run the script in Windows 7-32 bits, the "bug" is showed at 2 GB
> crunched  (OK, 2 GB is the max for a process)
> When I run the script in Windows 7-64 bits, the "bug" is showed at 4 GB
> crunched, on a computer with 8 GB.
>
> Why 4 GB, and no 2 GB or 8 GB?
>
>
> Sorry for my bad english, and good night.
>
> --
> Michel Claveau
>
>
> _______________________________________________
> python-win32 mailing list
> python-win32 at python.org
> http://mail.python.org/mailman/listinfo/python-win32
>



-- 
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
Using PostgreSQL is mostly about sleeping well at night.