-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Well, it seems that piece of information from /proc/meminfo tells us part of the problem. According to linux/Documentation/filesystems/proc.txt:
�Committed_AS: The amount of memory presently allocated on the system. ~ The committed memory is a sum of all of the memory which ~ has been allocated by processes, even if it has not been ~ "used" by them as of yet. A process which malloc()'s 1G ~ of memory, but only touches 300M of it will only show up ~ as using 300M of memory even if it has the address space ~ allocated for the entire 1G. This 1G is memory which has ~ been "committed" to by the VM and can be used at any time ~ by the allocating application. With strict overcommit ~ enabled on the system (mode 2 in 'vm.overcommit_memory'), ~ allocations which would exceed the CommitLimit (detailed ~ above) will not be permitted. This is useful if one needs ~ to guarantee that processes will not fail due to lack of ~ memory once that memory has been successfully allocated.�
By the way, I just ran pmap -d after restarting Mono and the results seem to be the same as before.
Thanks, - -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB7Bcp823633cP2P8RAjgjAJ9i33UiiRs3F+luTahLxQGYuxMHpACeNdis XfyenCPeTOTHHPfXDyC45Es= =j9b1 -----END PGP SIGNATURE-----
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
