S
Stevo
Hello,
I've been running Vista on a few PC's since release and haven't had any real
problems until SP1.
The issue I'm running into now is all of the PC's I've updated have a slow
memory leak since upgrading to SP1. After about 2-3 days of use,
explorer.exe is up to 400-500MB Commit & Working Set. This is up from
29M/49M a few hours into use after a fresh boot. Also, there is a svchost
network service that balloons up to >400MB.
The system becomes extremely sluggish and slow, with Physical Memory listing
as 70%+ versus 17-23% up to 2+ hours after a fresh restart.
Performing a fresh restart fixes the problem. explorer.exe shrinks to
normal 30-40MB usage and the one svchost is also small ~30MB working set. It
will be about 2-3 days before the system needs to be restarted once more as
it'll start becoming extremely slow/sluggish to use.
This only started after applying SP1. Prior, uptimes of >30+ days and the
system performed great. These systems are Home Premium, 32-bit and with 2
or 3 gigs of system ram each.
Any tips on trying to isolate what is causing explorer.exe to balloon so
much post SP1?
I've been running Vista on a few PC's since release and haven't had any real
problems until SP1.
The issue I'm running into now is all of the PC's I've updated have a slow
memory leak since upgrading to SP1. After about 2-3 days of use,
explorer.exe is up to 400-500MB Commit & Working Set. This is up from
29M/49M a few hours into use after a fresh boot. Also, there is a svchost
network service that balloons up to >400MB.
The system becomes extremely sluggish and slow, with Physical Memory listing
as 70%+ versus 17-23% up to 2+ hours after a fresh restart.
Performing a fresh restart fixes the problem. explorer.exe shrinks to
normal 30-40MB usage and the one svchost is also small ~30MB working set. It
will be about 2-3 days before the system needs to be restarted once more as
it'll start becoming extremely slow/sluggish to use.
This only started after applying SP1. Prior, uptimes of >30+ days and the
system performed great. These systems are Home Premium, 32-bit and with 2
or 3 gigs of system ram each.
Any tips on trying to isolate what is causing explorer.exe to balloon so
much post SP1?