Mark Thomas explains what are the common OutOfMemoryError failures that could appear when running Java applications, showing how to diagnose such errors. He also discusses the JVM and tc Server configuration parameters affecting memory settings.
Windows Presentation Foundation is quickly becoming well known for the ease in which memory leaks are introduced. Most of these leaks seem to come from the use or misuse of weak references, upon which WPF’s data binding technology is based. In the recent set of hotfixes many of these leaks are fixed.
Fabrice Marguerie, a software architect and consultant, wrote the article How to detect and avoid memory and resources leaks in .NET applications, published on MSDN. The article explains how memory and resource leaks can happen while programming for .NET and how to avoid them.
WPF, also known as Windows Presentation Foundation, represents the future of UI on the Windows platform. And if Microsoft has its way, its younger sibling Silerlight will take over the web and mobile markets. But like any new technology, it has some issues to work through including some rather serious memory leaks.
Quest Software recently released JProbe 8.0, a Java code, memory, and coverage profiler. While JProbe has been one of the leading Java profiling tools since the late 1990's, JProbe 8.0 aims to help Quest regain the leadership position in the profiling market with new Eclipse integration and a more competitive price point.
Steven Haines from Quest has published an article demonstrating the use of performance analysis tools in the continuous build cycle as best practice and makes some thought provoking points about the cost of not doing so.
Performance is a major issue for some Rails application. BleakHouse is a plugin that helps you find memory leaks, without using Ruby's ObjectSpace introspection.
A problem with .NET that isn't talked about is the problems caused by using dynamic code generation. In a nut shell, dynamic code generation, which is used in XML Serialization, Regular Expressions, and XSLT transformations, can lead to memory leaks.
Scott Laird was dealing with the difficulties of finding memory leaks in his Rails apps and came up with solution. Scott put the code for his solution up on his blog, respondents have already called it an essential tools they'll use on their projects going forward, and Scott promised to package it up as a plugin eventually.
