http://blog.dynatrace.com/2009/02/12/sharepoint-identifying-memory-problems-introduced-by-custom-code/ Sat, 11 Feb 2012 09:39:39 +0000 hourly 1 http://wordpress.org/?v=3.1.3 http://blog.dynatrace.com/2009/02/12/sharepoint-identifying-memory-problems-introduced-by-custom-code/comment-page-1/#comment-19911 Sharepoint Code Mon, 13 Sep 2010 10:23:17 +0000 http://blog.dynatrace.com/?p=320#comment-19911 This was a big deal for us - we wrote a custom menu system that wasn't disposing of SPWebs and was a disaster performance wise, a good post - cheers :D This was a big deal for us – we wrote a custom menu system that wasn’t disposing of SPWebs and was a disaster performance wise, a good post – cheers

]]> http://blog.dynatrace.com/2009/02/12/sharepoint-identifying-memory-problems-introduced-by-custom-code/comment-page-1/#comment-13748 How to avoid the Top 5 SharePoint Performance Mistakes Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog) Fri, 19 Mar 2010 13:55:48 +0000 http://blog.dynatrace.com/?p=320#comment-13748 [...] Further reading: Identifying memory problems introduced by custom code [...] [...] Further reading: Identifying memory problems introduced by custom code [...]

]]> http://blog.dynatrace.com/2009/02/12/sharepoint-identifying-memory-problems-introduced-by-custom-code/comment-page-1/#comment-1257 Rien de spécial » Blog Archive » Disposing objects in Sharepoint Fri, 27 Feb 2009 07:44:20 +0000 http://blog.dynatrace.com/?p=320#comment-1257 [...] where SPDisposeCheck tool may become handy. On a broader scope, identifying memory problems is a great article. this is done by the .net garbage collector and actually the .NET framework does [...] [...] where SPDisposeCheck tool may become handy. On a broader scope, identifying memory problems is a great article. this is done by the .net garbage collector and actually the .NET framework does [...]

]]>