Search

Report Viewer 2010 SP1 Memory Leak by MikeGCompass

Closed
as Deferred Help for as Deferred

38
0
Sign in
 to vote
Type: Bug
ID: 666364
Opened: 5/3/2011 3:14:44 AM
Access Restriction: Public
0
Workaround(s)
18
User(s) can reproduce this bug
Hi,
I have submitted this before as a post on the end of another similar bug, so sorry if this is a duplicate. It was flagged as fixed but I don't think it is or at least my issue is a different bug.
In an attached sample project...
I have 2 very simple reports one with an expression and another almost identical but it doesn't contain any report expressions.

ReportBad.rdlc has 1 expression and everytime you generate the PDF it grows in memory, so after a few executes you can have my simple EXE holding on to 1GB or more of memory.

ReportGood.rdlc has 0 expressions and everytime you generate it does not grow in memory.

Thus I conclude using expression columns causes some resources never to be released, even when you dispose the report viewer control.

This is a big issue for us as we use report viewer to generate pdf files sometimes in a client sometimes on a server.
Details (expand)

Visual Studio/Silverlight/Tooling version

Visual Studio 2010 SP1

What category (if any) best represents this feedback?

Performance

Steps to reproduce

Get my sample project (see attached zip)

Details: Generate a PDF file using the Report Viewer control from an rdlc file that has 1 or more expressions in it.

Product Language

English

Operating System

Windows 7

Operating System Language

English (UK)

Actual results

Excessive memoery usage, memory never reclaimed, just keeps on growing.

Expected results

Reasonable memory usage.
File Attachments
File Name Submitted By Submitted On File Size  
ReportViewerTest.zip MikeGCompass 5/3/2011 3.51 MB
Sign in to post a comment.
Posted by Microsoft on 4/20/2012 at 10:18 AM
Thank you for your feedback, I am sorry if I was not clear before please allow me to clarify; fixing this issue involve in architectural change, at the current release stage we cannot address this issue. We are considering fixing it for next major release.

Regards,
SQL Server Reporting Services.
Posted by MikeGCompass on 3/29/2012 at 2:11 AM
Hi,
Just tested the VS 11 Beta report viewer DLLs with my test app (attached to this connect issue)
Still seems to be broken, namely massive difference in memery use when using the "badReport.rdlc" file.

Hope you get this fixed in the final release.
It really does make using this DLL a huge risk for us and having to tell our customers to regularly restart the windows service that generates PDFs is rather embarasing.

Thanks,
Mike G
Posted by Microsoft on 3/28/2012 at 6:29 PM
Thank you for your feedback, we conducted investigation and unfortunately fixing this issue at the stage is very risky, we are considering fixing it in the next release. We will continue monitor customer feedback on the subject.

Regards,
SQL Server Reporting Services.
Posted by Johannes Gustafsson on 11/10/2011 at 5:37 AM
We have encountered memory leaks as well. We've been using Report Viewer 2010 SP1 for a while but only in .net 3.5 where we did not have any issues. However, when we upgraded to .net 4 we began experiencing leaks. Using dotTrace we have found that the entire LocalReport is stuck in memory. This means that we are stuck on .net 3.5 until this issue is resolved.
Posted by Zamir Khan on 9/26/2011 at 3:17 PM
We are experiencing the same issue. VS 2010 SP1 using a ReportViewer to render a LocalReport. Every time the report is rendered, even without a data set attached to it, memory grows by several MB. This memory is not reclaimed even by forcing a garage collection. This bug pretty much renders the Report Viewer unusable for us until it is fixed.
Posted by piyushtrivedi on 8/10/2011 at 12:38 PM
Hi ,

We have same memory consumption issue in our application. We are using MS 2005 reporting services that give in memory exception issue.
Currently, Our application is hosted on Production environment . Please help us to find out the root cause.

Thank you.

Posted by MikeGCompass on 6/24/2011 at 2:59 AM
Any news yet, have you managed to replicate this MS?
We really would like a fix for this please or even a workaround etc...
Posted by McMain on 6/24/2011 at 2:36 AM
Hi guys,

I'm wondering if you have made some progress on this issue. For us this is also a major issue,
Regards,
Posted by Microsoft on 5/3/2011 at 11:56 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by Microsoft on 5/3/2011 at 4:13 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement