igor0
13
I think the problem is in the “interpretation” of the values.
Some heaps are allocated with “maximum size limit” - however, the diagnostic tool considers the limit to be the size of memory that is commited - which is not true.
I have a Win98SE system here, with 128MB of RAM. When I check the system status right after start, I can see: 58MB Unused Physical Memory, 24MB Disk Cache Size, the swap file is 0 bytes long.
Heap Size reported by FreshDiagnoze for ashServ.exe is 110MB… which somehow doesn’t fit the numbers above. I’m not saying it’s the fault of FreshDiagnoze - I’m using a tool called ATM and it reports similar numbers. Just the “allocated” heap doesn’t necessarily mean the memory is really used (commited).