mrimer wrote:
When I use the files you gave me, the app only reaches ~400MB virtual.
<
redundant>
As I said in my last edit to my previous post - don't trust Task Manager, watch the process in Process Explorer...
<
/redundant>
EDIT: On closer inspection, what taskman calls "
VM Size"
is called "
Private Bytes"
in PE, whereas "
Virtual Size"
doesn't seem to have an equivalent in taskman...
Also, it looks like the integrity check is going to run for quite a while...
EDIT: Also, to quote
this post from the cygwin mailing list:
"procexp's "virtual size" is simply a representation of the amount of virutal memory that has been allocated to the process. Virtual memory is not real memory and it only means that X number of pages have been allocated, it says absolutely nothing about the actual memory used by the process, and you should ignore it completely unless you have a specific reason to need to know about it.
If I parse that correctly, this would mean that DROD needs almost 2GB of address space (the maximum a process can normally get under 32-bit Windows), but only uses 622MB - I guess the rest is going to waste due to memory fragmentation, i.e. lots of small holes between the allocated areas that are too small for DROD to be used but of course exhaust address space due to the lack of a compacting garbage collector...
EDIT: Seems to be the perfect use case for
Valgrind - too bad it's only available for Linux... and I'm not sure if both DROD and Valgrind run under CoLinux...
np: SCSI-9 - Sweets And Love (The Line Of Nine)
____________________________
"
I'm not anti-anything, I'm anti-everything, it fits better."
- Sole
R.I.P. Robert Feldhoff (1962-2009)
[Last edited by Briareos at 07-27-2006 09:20 PM]