Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage Memory Leaks Content on InfoQ


RSS Feed
  • Infer# Brings Facebook's Infer Static Analyzer to C# and .NET

    With Infer#, Microsoft extends the choice of static analyzers available within the .NET ecosystem by bringing Facebook Infer's inter-procedural static analysis capabilities to it.

  • C++ Core Guidelines will Help Writing Good Modern C++

    As announced at CppCon, Bjarne Stroustrup and Herb Sutter have started working on a set of guidelines for modern C++. The goal of this effort is improving how developers use the language and help ensuring they write code that is type safe, has no resource leaks, and is as much as possible free of programming logic errors.

  • .NET Memory Profiling in Visual Studio 2013

    Visual Studio 2013 comes with a better memory profiler for .NET applications, but it is still far behind the other commercial offerings.

  • JavaScript Memory Analyzer in Visual Studio 2012 Identifies Leaks in Windows Store Apps

    Visual Studio 2012 Update 1 includes a new JavaScript Memory Analyzer for Windows 8 which identifies potential memory leaks to enable developers to fix their apps before submission to Windows Store.

  • Google Open Sources Leak Finder, a JavaScript Tool for Detecting Memory Leaks

    Google has open sourced Leak Finder, a tool inspecting the heap of JavaScript applications in order to find memory leaks.

  • Weak Events in WPF 4.5

    .NET 4.5 brings with it a generic version of WeakEventManager for WPF developers. In addition to not needing the event-specific subclass, this version also dispenses with the need for listener interfaces.

  • Three Hotfixes for WPF Memory Leaks

    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.

  • Dealing with Memory Leaks in .NET

    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.

  • Serious Memory Leaks Plague WPF

    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.

  • Presentation: Conceptual Algorithms

    In this talk from RubyFringe, Tom Preston-Werner talks about how he uses the scientific method for tracking down software problems. He demonstrates how he used this approach to track down a particularly sneaky memory leak in a Ruby app, and more.

  • JProbe 8.0: The Java code, memory, and coverage profiler is back

    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.

  • Review: Continous Performance Management

    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.

  • Find Memory Leaks in Your Rails Application with BleakHouse

    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.

  • .NET Memory Leaks

    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.

  • A Rails memory leak profiling solution

    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.


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.