 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Performance / September 2005large object memory leak?
Folks, There was an issue in 1.0 with arrays greater than 16MB not being collected. Was this completely fixed in 1.1 or just improved. Anyone have the details on this? -arnie who knows? MS claims its fixed, I still see folk complaining about it in here. So it depends on who is doing the asking. What problems are you seeing?  SignatureRegards, Alvin Bruney [MVP ASP.NET] [Shameless Author plug] The Microsoft Office Web Components Black Book with .NET Now Available @ www.lulu.com/owc Forth-coming VSTO.NET - Wrox/Wiley 2006 ------------------------------------------------------- > Folks, > [quoted text clipped - 5 lines] > > -arnie We are seeing the leak on 1.1. Large arrays are not being cleaned up. -jeff > who knows? MS claims its fixed, I still see folk complaining about it in > here. So it depends on who is doing the asking. What problems are you [quoted text clipped - 10 lines] >> >> -arnie yup. Report it to microsoft thru a trouble ticket. Maybe, eventually, they will repair the annoyance. SignatureRegards, Alvin Bruney [MVP ASP.NET] [Shameless Author plug] The Microsoft Office Web Components Black Book with .NET Now Available @ www.lulu.com/owc Forth-coming VSTO.NET - Wrox/Wiley 2006 ------------------------------------------------------- > We are seeing the leak on 1.1. > [quoted text clipped - 16 lines] > >> > >> -arnie on second thought, since you came here to get help why don't you explain what it is you are doing and what you are seeing that leads you conclude that there is a memory leak. I dear say that 16mb in an array seems like a suspect design but I'm not familiar with your architecture so I won't say it out loud. SignatureRegards, Alvin Bruney [MVP ASP.NET] [Shameless Author plug] The Microsoft Office Web Components Black Book with .NET Now Available @ www.lulu.com/owc Forth-coming VSTO.NET - Wrox/Wiley 2006 ------------------------------------------------------- > yup. Report it to microsoft thru a trouble ticket. Maybe, eventually, they > will repair the annoyance. [quoted text clipped - 19 lines] > > >> > > >> -arnie > We are seeing the leak on 1.1. > > Large arrays are not being cleaned up. You need to find out where they are rooted (if they are rooted.) If they aren't rooted, it's possible that you might be ecountering a bug that causes Timers not to fire and objects to not get cleaned up. I've encountered this issue many times over the past few months. http://support.microsoft.com/Default.aspx?id=900822 Note that this is a post-sp1 fix. The best thing for you to do would be to get a dump and use SOS to analyze your memory usage. SignatureJim Cheshire JIMCO Software http://www.jimcosoftware.com FrontPage add-ins for FrontPage 2000 - 2003 Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.