Ouch, please ignore my previous
email. The root cause was CraftedMemoryPolicy's default of 160000000, which was
being set midway through and wasn't enough for us to complete the load.
-Boris
--
DeepCove Labs Ltd.
+1 (604) 689-0322
4th floor, 595 Howe Street
Vancouver, British Columbia
Canada V6C 2T5
http://tinyurl.com/r7uw4
PacNet Services (Europe) Ltd.
+353 (0)61 714-360
Shannon Airport House, SFZ
County Clare, Ireland
http://tinyurl.com/y952amr
CONFIDENTIALITY NOTICE
This email is intended only for
the persons named in the message header. Unless otherwise indicated, it
contains information that is private and confidential. If you have received it
in error, please notify the sender and delete the entire message including any
attachments.
Thank you.
From: Boris Popov, DeepCove Labs (YVR)
Sent: 12 February 2010 11:14
To: [hidden email]
Subject: [7.7] Emergency: No Space Left, but a touch too early?
I've run into this a few times now, trying to get our
codebase loaded into 7.7 cleanly with all prereqs. Process Monitor Emergency:
No Space Left comes up, but from looking at it, it's a touch too early, because
the memory policy's max is set at 536MB, whereas process monitor and OS both
report ~150MB. Any ideas? Is this normal?
>wmic process where name="vwnt.exe" get name,
workingsetsize, peakvirtualsize
Name PeakVirtualSize
WorkingSetSize
vwnt.exe
252051456 171728896
Cheers,
-Boris
--
DeepCove Labs Ltd.
+1 (604) 689-0322
4th floor, 595 Howe Street
Vancouver, British Columbia
Canada V6C 2T5
http://tinyurl.com/r7uw4
PacNet Services (Europe) Ltd.
+353 (0)61 714-360
Shannon Airport House, SFZ
County Clare, Ireland
http://tinyurl.com/y952amr
CONFIDENTIALITY NOTICE
This email is intended only for the persons named in the
message header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please notify the
sender and delete the entire message including any attachments.
Thank you.
Locked
