Home Dashboard Directory Help
Search

Metafile memory issues by uler3161


Status: 

Closed
 as External Help for as External


1
0
Sign in
to vote
Type: Bug
ID: 780126
Opened: 2/27/2013 9:03:40 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I'm getting a generic GDI+ exception on some machines. It seems almost random. I don't seem to have much of an issue on my development machine, but I am running more memory and windows 7, whereas the users machine has less memory and is windows XP.

I've already tried to explain the issue on the MSDN forums, so it's easier for me to just post a link: http://social.msdn.microsoft.com/Forums/en-US/vsreportcontrols/thread/ce4b26e1-2c06-43c4-8531-40cdfa4809b9.

Since nobody has responded, I thought I would submit it as a bug. My feeling is that there is a memory leak somewhere, but as far as I know, I'm disposing everything correctly. So I don't believe it's in my code.

The looping code I posted in that thread will cause a generic GDI+ exception, however I don't know for sure that it's the same issue that my user is facing. It was the only way I thought I could make a reproducible demo. However, I don't see why I would have any issues redrawing the metafile onto a Graphics any number of times that I want to, so it seems a bit like a bug.

Also, this is .NET Framework 3.5, but apparently I can't select that in the Visual Studio/Team Foundation Server/.NET Framework Tooling Version box?
Details
Sign in to post a comment.
Posted by Microsoft on 2/27/2013 at 10:54 PM
The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
<http://msdn.microsoft.com/en-us/vstudio/cc136615.aspx>

Sorry for the inconvenience.
Posted by Microsoft on 2/27/2013 at 9:50 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.