Memory Analyzer 1.1

Memory Analyzer 1.1. was just released!
Check the New and noteworthy page and download it from here.

Extending the Eclipse Memory Analyzer

I usally don't post links here but I always wanted to describe here how to extend the Eclipse Memory Analyzer. Since there's now a Slide Deck available that describes briefly how it can be done at
http://www.slideshare.net/AJohnson1/extending-eclipse-memory-analyzer it's not that urgent anymore to post a description here ;-)


I believe there's a huge potential in extending MAT for specific use cases, such as Android, Jruby, Scala etc.

Talk at Eclipse demo camp in Mannheim

I will give a short talk/demo of how to use the Eclipse Memory Analyzer for analyzing android applications today, June 10 (19.00 - 21.30) in Mannheim, University A5, C013 at the demo camp event:

http://wiki.eclipse.org/Eclipse_DemoCamps_Helios_2010/Mannheim

Hope to see some of you there.
Markus

Android memory usage analysis slides available

Yesterday, I gave a talk at the mobile monday android developer day in Düsseldorf.The slides about analysing the memory usage of android applications with the Eclipse Memory Analyzer are available now. Note it might be worth to download the pdf because it contains some notes.
The slides should be interesting for general java developers, not only for android developers.
Also, I want to thank everyone who showed up. It was great talking to all of you!

New Memory Analyzer release

A new version of the Eclipse Memory analyzer is available for download and from the update site.
This is the last 0.8 release and from now on working on the 1.0 release will start.
This is a bug fix release and here's the list of the most important bugs fixed:

294350 StackOverflowError in ArrayUtils.hybridsort

270777 The dialog font not apply to the ArgumentWizard

281311 Merged Paths from GC roots calculation may slow down the Leak Suspects report

273915 New resolvers URL, Point and Rectangle

299283 Allow dynamic specification of file extensions for parsers

299497 DTFJ Adapter retains memory

272887 No JvmInfo in Heap Dump details pane

274539 Overview pane is missing scroll bars

297458 Single object queries have a confusing dialog box

254864 Leaking Memory after closing the Heap Dump Editor

First talk about analysing Memory usage on android ever?

I am pleased to announce that I will be speaking  at the MobileMonday Developer Day
in Düsseldorf on 23.2.2010. 
The talk (in German in English!)  will be about analyzing the memory usage analysis of android applications using the Eclipse Memory Analyzer.

Titel:
Optimierung des Speicherverbrauchs von Android Anwendungen mit Hilfe des Eclipse Memory Analyzers

Abstract:
Die Minimierung des Speicherverbrauchs ist ein sehr wichtiger Aspekt bei der Entwicklung performanter Android Anwendungen.
Im Vortrag werden die wichtigsten Konzepte zur Analyse des Speicherverbrauchs mittels Heap Dumps vorgestellt.
Anhand von realen Android Anwendungen wird live demonstriert wie der Eclipse Memory Analyzer  die Identifikation von "Hot Spots" unterstützt und damit eine wichtige Grundlage zur Optimierung liefert. 

Eclipse Memory Analyzer, 10 useful tips/articles

The Eclipse Memory Analyzer has been shipped with Eclipse 3.5 Galileo and I planned to start a new series here about memory usage antipatterns and how to analyze them with MAT.
Unfortunately I'm pretty busy these days and I will need more time for those posts.
But, due to popular demand I decided it would make sense to post some good links (ok, I admit some of them are from myself) about how to use the Eclipse Memory Analyzer.
Please forgive me if I missed some important ones, but I'm really hungry now and therefore just stopped after 10 tips ;)

1. How to really measure memory usage: The absolute fundamentals
2. Check the online help. It has a pretty good introduction chapter.
3. Memory leaks are easy to find: Learn how to analyze memory leaks
4. Check also one click leak analysis if this is your problem :]
5. Memory usage analysis: Learn the fundamental approach for finding the owner of a set of objects
6. A typical issue in Goggles Android UI framework: Learn how to analyze memory usage on Googles android platform. Shows a typical issue that can be solved by using lazy initialization.
7. Never forget to take a look at your Strings: Learn why String.intern() can be useful
8. A tip for analysis Equinox based applications: Learn about a special feature for Eclipse based applications.
9. Analysing perm size/classloader  problems: Perm size problems can be nasty. Check why a Jruby core developer likes MAT ;)
10. If you like webinar's here's an introduction presented by the developers.

Just read my memory related blogs: Oh that was number 11, but who cares? ;)