How to trace possible memory leak in ReportViewer 2010 ASP.net control

I have a simple ASP.net report that uses ReportViewer 2010 ASP.net control and local report.
In the early morning, the report runs fine, but as the day progresses, performance degrades to terrible.

The web page renders filne except for the ReportViewer control.  

Any advice on tracing and dcoumenting the issue would be most appreciated.

Thank you.
JEClark1Asked:
Who is Participating?
 
deightonprogCommented:
is the amount of memory in use increasing?  

you can investigate these things using SOS, adPlus and windbg - all highly involved I'm afraid.

Is this a third party control or your control?  
0
 
JEClark1Author Commented:
Amount of memory is increasing.

This is a Microsoft control, available here:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a941c6b2-64dd-4d03-9ca7-4017a0d164fd&displaylang=en

Thank youl
0
 
deightonprogCommented:
there seems to be talk of this issue, but they claim it is fixed in version 2010

http://connect.microsoft.com/VisualStudio/feedback/details/510243/report-viewer-has-memory-leak-in-local-report-mode
0
 
JEClark1Author Commented:
These were good things to look at but the problem remained unresolved.  I am not going to rely on this control
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.