news.eclipse.technology.memory-analyzer http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/maillist.html NewsGroup: news.eclipse.technology.memory-analyzer en-us Wed, 16 Sep 2009 09:50:22 GMT Wed, 16 Sep 2009 09:50:22 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) news.eclipse.technology.memory-analyzer http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/maillist.html [news.eclipse.technology.memory-analyzer] Re: Any plans to support C++? http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00355.html Hi Marc, with respect to a developer guide, there is some room for improvement - to put it nicely. Let me try to give you some hints to get started. To setup your local development, follow these instructions on the WIKI: http://wiki.eclipse.org/index.php?t... Hi Marc,
with respect to a developer guide, there is some room for improvement - to put it nicely. Let me try to give you some hints to get started.

do you have a developer guide? so far, I found your slides showing APIs. is there any further explanation (eg Collections, Finalizer.. Snapshot, Parser?)? 

To setup your local development, follow these instructions on the WIKI:
http://wiki.eclipse.org/index.php?title=MemoryAnalyzer/Contributor_Reference

The follow the code. Basically there are two ways to extend the Memory Analyzer. One way is adding features which operate on the heap dump. We call those "queries". All the (context) menus like "Java Basics" and "Java Collections" etc. are implemented as queries.

Queries can be found in these packages:
org.eclipse.mat.inspections.*

The queries use the following API to implement their functionality:
org.eclipse.mat.snapshot.*
org.eclipse.mat.snapshot.model.*

The queries work like this: implement the IQuery interface and configure the extension in the plugin.xml. To define input parameter, use the @Argument annotation. Based on these annotations, we decided whether the query is shown in a particular context menu.


The second way to extend MAT is by providing a heap dump reader. Currently there are two supported formats: hprof and dtfj. The implementation can be found in the two projects org.eclipse.mat.hprof and org.eclipse.mat.dtfj. They implement the parser interface, which in turn in found in the org.eclipse.mat.parser project.

In the case of HPROF, the "music plays" in the HprofIndexBuilder class. This is called to initially build the indeces (inbound, outbound object graphs etc.) and the re-create the Java classes from the heap dump.

The second class is called HprofHeapObjectReader and is used to create objects representing Java instances while doing the analysis - e.g. reading the attributes, field values, etc.


also, am unable to find source code in cvs. aren't you under cvsroot/technology? 

We use a subversion repository. The source is located here:
http://dev.eclipse.org/svnroot/technology/org.eclipse.mat


Andreas.


]]> Wed, 16 Sep 2009 09:35:52 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00355.html andreas.buchen@xxxxxxx (Andreas Buchen) [news.eclipse.technology.memory-analyzer] Re: Any plans to support C++? http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00354.html thanks. do you have a developer guide? so far, I found your slides showing APIs. is there any further explanation (eg Collections, Finalizer.. Snapshot, Parser?)? also, am unable to find source code in cvs. aren't you under cvsroot/technology? thaks, Marc thanks.
do you have a developer guide? so far, I found your slides showing APIs. is there any further explanation (eg Collections, Finalizer.. Snapshot, Parser?)?

also, am unable to find source code in cvs. aren't you under cvsroot/technology?

thaks,
Marc


]]> Thu, 10 Sep 2009 05:37:03 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00354.html Marc.Tolentino@xxxxxxx ( Marc) [news.eclipse.technology.memory-analyzer] Re: java.lang.Integer: 16 bytes or 24? http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00353.html It looks like I only see this on older versions of MAT and it is already fixed on the newer version that I tried. 16 bytes is the right number. It looks like I only see this on older versions of MAT and it is already fixed on the newer version that I tried. 16 bytes is the right number.



]]> Tue, 08 Sep 2009 19:34:19 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00353.html randallt@xxxxxxx (Randall Theobald) [news.eclipse.technology.memory-analyzer] java.lang.Integer: 16 bytes or 24? http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00352.html I wrote a simple program to play around with some of my memory analysis tools. I happened upon an inconsistency with MAT. One of my tools says that Integer objects take up 16 bytes per instance. Docs I've found online seem to support this. However, MAT is ... I wrote a simple program to play around with some of my memory analysis tools. I happened upon an inconsistency with MAT. One of my tools says that Integer objects take up 16 bytes per instance. Docs I've found online seem to support this. However, MAT is showing 24 bytes per instance. Which is correct?



]]> Tue, 08 Sep 2009 18:53:40 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00352.html randallt@xxxxxxx (Randall Theobald) [news.eclipse.technology.memory-analyzer] Re: Any plans to support C++? http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00351.html Sorry, no plans at all. Just no Know-how. Could one reuse stuff? Maybe. There is a Plug-in mechanism, but the Memory model is probably too Java specific. Take a look at the org.eclipse.mat.api bundle to get an idea of the API. Send an email if you have que... do you have any plans adding C++ specific memory analyzer? if no, how easy/difficult would it be to re-use existing plug-ins?
Sorry, no plans at all. Just no Know-how. Could one reuse stuff? Maybe. There is a Plug-in mechanism, but the Memory model is probably too Java specific. Take a look at the org.eclipse.mat.api bundle to get an idea of the API. Send an email if you have questions.


]]> Thu, 03 Sep 2009 18:17:45 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00351.html andreas.buchen@xxxxxxx (Andreas Buchen) [news.eclipse.technology.memory-analyzer] Re: Analyzing from 64bit to 32bit http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00350.html The Index files - once created - work on all machines. Just copy everything to the 32bit box. The Index files - once created - work on all machines. Just copy everything to the 32bit box.


]]> Thu, 03 Sep 2009 18:11:13 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00350.html andreas.buchen@xxxxxxx (Andreas Buchen) [news.eclipse.technology.memory-analyzer] Analyzing from 64bit to 32bit http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00349.html Hello, We kept running in to Not enough Memory errors on our 32bit machines when running MAT, so we processed the file on a 64-bit headless machine. Is there a way to load the output (.index) files in MAT on a 32bit machine? Browsed the wiki and found noth... Hello,
We kept running in to Not enough Memory errors on our 32bit machines when running MAT, so we processed the file on a 64-bit headless machine. 

Is there a way to load the output (.index) files in MAT on a 32bit machine? Browsed the wiki and found nothing.

]]> Thu, 03 Sep 2009 12:56:36 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00349.html royrusso@xxxxxxx (royrusso) [news.eclipse.technology.memory-analyzer] Any plans to support C++? http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00348.html hi, do you have any plans adding C++ specific memory analyzer? if no, how easy/difficult would it be to re-use existing plug-ins? thanks, Marc hi,
do you have any plans adding C++ specific memory analyzer? if no, how easy/difficult would it be to re-use existing plug-ins?

thanks,
Marc


]]> Wed, 02 Sep 2009 15:34:55 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00348.html Marc.Tolentino@xxxxxxx ( Marc) [news.eclipse.technology.memory-analyzer] Re: can we use Ant to run the memory analyzer http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00347.html Be sure to update it to the right version numbers, but something like this should work: <java classname="org.eclipse.equinox.launcher.Main" fork="true" failonerror="true"> <arg value="-application" /> ;arg value="org.eclipse.mat.api.parse" /> <arg value=uo... How can we use Ant to run the memory analyzer?
Be sure to update it to the right version numbers, but something like this should work:

<java classname="org.eclipse.equinox.launcher.Main" fork="true" failonerror="true">
<arg value="-application" />
<arg value="org.eclipse.mat.api.parse" />
<arg value="path/to/dump" />
<arg value="org.eclipse.mat.api:suspects" />

<classpath>
<pathelement location="${matLocation}/plugins/org.eclipse.equinox.launcher_${equinoxLauncherPluginVersion}.jar" />
</classpath>
</java>





]]> Tue, 25 Aug 2009 12:20:58 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00347.html andreas.buchen@xxxxxxx (Andreas Buchen) [news.eclipse.technology.memory-analyzer] Re: cmdline way to open MAT with a dump and save reports in default format http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00346.html On win32, just run the script ParseHeapDump.sh &lt;path to heap dump&gt; [report]* The leak report has the id org.eclipse.mat.api:suspects To run MAT with any script, use the java command line as described here: http://wiki.eclipse.org/index.php/MemoryAnalyzer/F... Is there a way to run the MAT from cmdline with the dump file to avoid file -> open-> dump file and to export in a default format without navigating the menu. 

On win32, just run the script

 ParseHeapDump.sh <path to heap dump> [report]*

The leak report has the id org.eclipse.mat.api:suspects


To run MAT with any script, use the java command line as described here:
http://wiki.eclipse.org/index.php/MemoryAnalyzer/FAQ#How_to_run_on_64bit_VM_while_the_native_SWT_are_32bit


To run within ANT, use an <exec /> task.


]]> Tue, 25 Aug 2009 12:18:30 GMT http://dev.eclipse.org/mhonarc/newsLists/news.eclipse.technology.memory-analyzer/msg00346.html andreas.buchen@xxxxxxx (Andreas Buchen)