|
My company just rolled out a beta win7x64 corporate image. I've been using it since Tuesday. I am getting errors that point me towards there being memory fragmentation at the system level.
In particular, the JVM won't run because it can't allocate object heap space and VirtualBox will fail loading a 1GB ram VM, when I have the following (rough) memory stats in resource monitor:
in use:1.9GB Modified: 100MB Standby: 3.1GB Free .9GB
The free memory creeps down until it's gone, the standby never reduces, and I get a error saying there is no memory and the VM kicks the bucket. I need help finding out what is fragging memory so I can convince my IT that it is a problem, and give them a clue where to look.
So, does anyone know any good tools for finding the cause?
Opacity, the new Transparency.
|
|
|
|
|
Try here[^] for the Win 7 SDK, as I think they included a memory testing utility in it.
Other option would be to try and use BootVis to see if a driver is not releasing from bootup or what not.
Try clearing the startup programs and opening Taskbar and seeing what's running for processes/services.
fyi...I've even seen svchost.exe' fill up on RAM from leftover Window's Updates.
Something worth reading, albeit it's invincible!
|
|
|
|
|
Thanks, I will give it a try.
Opacity, the new Transparency.
|
|
|
|