app running slowly after used for a while/memory mgt

  • Thread starter Thread starter TS
  • Start date Start date
T

TS

I have an application that is in production and every so often, i am told it
becomes slow and nearly unresponsive, so they have to reboot it, then it
works fine. I am wondering what the problem is. i imagine the code has a
memory leak somewhere. i can't confirm that a lot of memory is used up on
the system as i have never seen the system in this state; all i know is the
slow and non-responsiveness.

I know for mem problems you usually look towards unmanaged objects like
files being opened. Is there any other thing i can do to figure out what is
going on? free third party produts?


ALSO:
I notice when i leave my computer on and VS.net open, the next day or so,
when i come in to work on my machine, i notice it very slow and when i build
a project, it takes about 20 seconds that normally takes 1 second. I'm
wondering are these 2 issues related? Is it a .net thing?

thanks
 
If your client is particularly helpful, you could get them to create a
minidump of your application the next time it becomes slow. You can then use
WinDBG and the SOS extension to find out if it is related to objects that
aren't being collected. Google for AutoDump+ and WinDBG - both are available
free from Microsoft's website.

A good guide to WinDBG is available here:
http://mtaulty.com/blog/archive/2004/08/03/609.aspx

I would take a guess that the other issue you describe is just Visual Studio
being paged to disk overnight.
 
You need to download Debugging Tools for Windows from
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx onto the
machine that will create the dump.

Then run the following command once the process is running slowly:

C:\Windows\System32\cscript.exe "C:\Program Files\Debugging Tools for
Windows\adplus.vbs" -Hang -p <ProcessId> -quiet -o <OutputDir>

for example:

C:\Windows\System32\cscript.exe "C:\Program Files\Debugging Tools for
Windows\adplus.vbs" -Hang -p 2055 -quiet -o C:\Temp

You can find the process id in task manager.

Hope this helps.

Regards,
Matt Garven
 
thank you!

Matt Garven said:
You need to download Debugging Tools for Windows from
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx onto the
machine that will create the dump.

Then run the following command once the process is running slowly:

C:\Windows\System32\cscript.exe "C:\Program Files\Debugging Tools for
Windows\adplus.vbs" -Hang -p <ProcessId> -quiet -o <OutputDir>

for example:

C:\Windows\System32\cscript.exe "C:\Program Files\Debugging Tools for
Windows\adplus.vbs" -Hang -p 2055 -quiet -o C:\Temp

You can find the process id in task manager.

Hope this helps.

Regards,
Matt Garven
Click to expand...
 
does anyone else have any input on why VS runs real slow for a while in the
morning when i leave computer on?
 
Hi TS,

For this issue, I suggest you check if there is any background process
running all night, which costs much memory usage and causes the system slow
done.

Also, does VS.net still takes 20 seconds for the second and following
build? Actually, for Windows system, it will poll a lot of physical pages
from memory to the disk paging file to reduce memory usage for long did not
used application, so after a long time, the VS.net's memory pages are
stored on the paging file, and the first build will cause the system to
retrieve the memory pages from disk paging file again, which will take a
far long time than normal time.

Hope this helps.
==================================================
Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top