<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Memory Analyzer News</title>
	<atom:link href="http://dev.eclipse.org/blogs/memoryanalyzer/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://dev.eclipse.org/blogs/memoryanalyzer</link>
	<description>News from the Memory Analyzer</description>
	<pubDate>Sat, 07 Nov 2009 18:05:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>Comment on The Power of Aggregation: Making sense of the Objects in a Heap Dump by My memory leak in pictures &#187; ghidinelli.com</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/08/the-power-of-aggregation-making-sense-of-the-objects-in-a-heap-dump/#comment-192</link>
		<dc:creator>My memory leak in pictures &#187; ghidinelli.com</dc:creator>
		<pubDate>Tue, 25 Aug 2009 18:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/08/the-power-of-aggregation-making-sense-of-the-objects-in-a-heap-dump/#comment-192</guid>
		<description>[...] of the techniques I read about was to use the right-click menu and choose to look at an object by Merging Shortest Path to GC [...]</description>
		<content:encoded><![CDATA[<p>[...] of the techniques I read about was to use the right-click menu and choose to look at an object by Merging Shortest Path to GC [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About Querying Objects from a Heap Dump&#8230; by Andreas Buchen</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/09/03/about-querying-objects-from-a-heap-dump/#comment-184</link>
		<dc:creator>Andreas Buchen</dc:creator>
		<pubDate>Mon, 17 Aug 2009 08:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/09/03/about-querying-objects-from-a-heap-dump/#comment-184</guid>
		<description>As of today, it is not possible to retrieve a particular array element. I have created this bugzilla entry to track this feature request: https://bugs.eclipse.org/bugs/show_bug.cgi?id=286771</description>
		<content:encoded><![CDATA[<p>As of today, it is not possible to retrieve a particular array element. I have created this bugzilla entry to track this feature request: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=286771" rel="nofollow">https://bugs.eclipse.org/bugs/show_bug.cgi?id=286771</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About Querying Objects from a Heap Dump&#8230; by Sam</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/09/03/about-querying-objects-from-a-heap-dump/#comment-172</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Tue, 04 Aug 2009 21:06:20 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/09/03/about-querying-objects-from-a-heap-dump/#comment-172</guid>
		<description>Hi..what is the syntax to retrieve a particular array element?  for example, if I want to get the value of some string that is stored in as the third entry of an array.</description>
		<content:encoded><![CDATA[<p>Hi..what is the syntax to retrieve a particular array element?  for example, if I want to get the value of some string that is stored in as the third entry of an array.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Automated Heap Dump Analysis: Finding Memory Leaks with One Click by Eclipse Memory Analyzer &#8211; best tool for investigating huge heap dumps from production &#171; Alex Torex Blog</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-137</link>
		<dc:creator>Eclipse Memory Analyzer &#8211; best tool for investigating huge heap dumps from production &#171; Alex Torex Blog</dc:creator>
		<pubDate>Mon, 06 Jul 2009 09:24:28 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-137</guid>
		<description>[...] Automated Heap Dump Analysis: Finding Memory Leaks with One Click     Posted by alextorex Filed in IT   Leave a Comment &#187; [...]</description>
		<content:encoded><![CDATA[<p>[...] Automated Heap Dump Analysis: Finding Memory Leaks with One Click     Posted by alextorex Filed in IT   Leave a Comment &#187; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Automated Heap Dump Analysis: Finding Memory Leaks with One Click by Eclipse Galileo: Nueva versión, corriendola en OSX &#124; KodeGeek</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-125</link>
		<dc:creator>Eclipse Galileo: Nueva versión, corriendola en OSX &#124; KodeGeek</dc:creator>
		<pubDate>Tue, 30 Jun 2009 01:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-125</guid>
		<description>[...] un trabajo tremendo (Yourkit se puede integrar con Eclipse también). Pero el hecho de que Eclipse la integre de una vez es super cómodo y [...]</description>
		<content:encoded><![CDATA[<p>[...] un trabajo tremendo (Yourkit se puede integrar con Eclipse también). Pero el hecho de que Eclipse la integre de una vez es super cómodo y [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Automated Heap Dump Analysis: Finding Memory Leaks with One Click by zx&#8217;s diatribe &#187; Eclipse Galileo Review</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-95</link>
		<dc:creator>zx&#8217;s diatribe &#187; Eclipse Galileo Review</dc:creator>
		<pubDate>Thu, 11 Jun 2009 20:55:58 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-95</guid>
		<description>[...] Finding Memory Leaks in One Click [...]</description>
		<content:encoded><![CDATA[<p>[...] Finding Memory Leaks in One Click [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Automated Heap Dump Analysis: Finding Memory Leaks with One Click by Myšlenky dne otce Fura &#187; Blog Archive &#187; Spring CgLib Dynamic AOP Proxies - proper Pointcut equals method is simply essential</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-80</link>
		<dc:creator>Myšlenky dne otce Fura &#187; Blog Archive &#187; Spring CgLib Dynamic AOP Proxies - proper Pointcut equals method is simply essential</dc:creator>
		<pubDate>Sat, 18 Apr 2009 20:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-80</guid>
		<description>[...] When analyzing generated heap dump I have found, that memory leak was caused by web application classloader, that managed thousands of CgLib dynamically generated classes. I was using Eclipse Memory Analyzer, that&#8217;s probably the best tool for memory heap dump analysis I have ever seen. It&#8217;s the third time it quickly identified the suspicious classes, by heuristic analysis called Leak suspect. [...]</description>
		<content:encoded><![CDATA[<p>[...] When analyzing generated heap dump I have found, that memory leak was caused by web application classloader, that managed thousands of CgLib dynamically generated classes. I was using Eclipse Memory Analyzer, that&#8217;s probably the best tool for memory heap dump analysis I have ever seen. It&#8217;s the third time it quickly identified the suspicious classes, by heuristic analysis called Leak suspect. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Automated Heap Dump Analysis: Finding Memory Leaks with One Click by Good Read: Find Memory Leaks with MAT &#124; twit88.com</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-48</link>
		<dc:creator>Good Read: Find Memory Leaks with MAT &#124; twit88.com</dc:creator>
		<pubDate>Tue, 17 Feb 2009 07:37:38 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/05/27/automated-heap-dump-analysis-finding-memory-leaks-with-one-click/#comment-48</guid>
		<description>[...] Automated Heap Dump Analysis: Finding Memory Leaks with One Click [...]</description>
		<content:encoded><![CDATA[<p>[...] Automated Heap Dump Analysis: Finding Memory Leaks with One Click [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Analyzing the Equinox Bundle Dependencies with Memory Analyzer by Elena Nayashkova</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/11/28/analyzing-the-equinox-bundle-dependencies-with-memory-analyzer/#comment-31</link>
		<dc:creator>Elena Nayashkova</dc:creator>
		<pubDate>Tue, 02 Dec 2008 08:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/11/28/analyzing-the-equinox-bundle-dependencies-with-memory-analyzer/#comment-31</guid>
		<description>&#62;it’s wonderful feature and would be great if MAT could simply plug into Plug-in registry, instead of reimplementing it.

MAT performs offline memory anylysis based on heap dumps (e.g. when you application crushed with an OutOfMemoryError). Thus, information about bundles is taken from the heap dump, not Eclipse's Plug-in Registry View. 
Of course, you have more options if you want to analyze the bundle dependencies in a running application, but one of them is to use Memory Analyzer:)</description>
		<content:encoded><![CDATA[<p>&gt;it’s wonderful feature and would be great if MAT could simply plug into Plug-in registry, instead of reimplementing it.</p>
<p>MAT performs offline memory anylysis based on heap dumps (e.g. when you application crushed with an OutOfMemoryError). Thus, information about bundles is taken from the heap dump, not Eclipse&#8217;s Plug-in Registry View.<br />
Of course, you have more options if you want to analyze the bundle dependencies in a running application, but one of them is to use Memory Analyzer:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Analyzing the Equinox Bundle Dependencies with Memory Analyzer by Jacek Pospychala</title>
		<link>http://dev.eclipse.org/blogs/memoryanalyzer/2008/11/28/analyzing-the-equinox-bundle-dependencies-with-memory-analyzer/#comment-30</link>
		<dc:creator>Jacek Pospychala</dc:creator>
		<pubDate>Mon, 01 Dec 2008 14:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://dev.eclipse.org/blogs/memoryanalyzer/2008/11/28/analyzing-the-equinox-bundle-dependencies-with-memory-analyzer/#comment-30</guid>
		<description>it's wonderful feature and would be great if MAT could simply plug into Plug-in registry, instead of reimplementing it. Hopefully it'll be possible soon (https://bugs.eclipse.org/bugs/show_bug.cgi?id=243439)</description>
		<content:encoded><![CDATA[<p>it&#8217;s wonderful feature and would be great if MAT could simply plug into Plug-in registry, instead of reimplementing it. Hopefully it&#8217;ll be possible soon (https://bugs.eclipse.org/bugs/show_bug.cgi?id=243439)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
