<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EurekaLog Blog &#187; memory leaks</title>
	<atom:link href="http://blog.eurekalog.com/tag/memory-leaks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.eurekalog.com</link>
	<description>A blog about the EurekaLog tool</description>
	<lastBuildDate>Tue, 27 Jul 2010 11:43:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Memory problems in Delphi apps &#8211; final article</title>
		<link>http://blog.eurekalog.com/memory-problems-in-delphi-apps-final-article/</link>
		<comments>http://blog.eurekalog.com/memory-problems-in-delphi-apps-final-article/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 23:01:33 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Delphi]]></category>
		<category><![CDATA[best practice]]></category>
		<category><![CDATA[EL 6.x]]></category>
		<category><![CDATA[how-to]]></category>
		<category><![CDATA[memory leaks]]></category>
		<category><![CDATA[other tools]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://blog.eurekalog.com/?p=339</guid>
		<description><![CDATA[I've published several articles already, which covers different aspects of memory issues. I'm going to give a short review of these articles first and then finish this series with current article. I've only mentioned most scary problems in the previous articles, dealing with simple cases first and leaving hard cases for later. Now it's time to deal with them, therefore finishing the series.]]></description>
		<wfw:commentRss>http://blog.eurekalog.com/memory-problems-in-delphi-apps-final-article/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Catching memory leaks, redux</title>
		<link>http://blog.eurekalog.com/catching-memory-leaks-redux/</link>
		<comments>http://blog.eurekalog.com/catching-memory-leaks-redux/#comments</comments>
		<pubDate>Tue, 16 Feb 2010 02:00:54 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Delphi]]></category>
		<category><![CDATA[best practice]]></category>
		<category><![CDATA[how it works]]></category>
		<category><![CDATA[how-to]]></category>
		<category><![CDATA[memory leaks]]></category>
		<category><![CDATA[other tools]]></category>

		<guid isPermaLink="false">http://blog.eurekalog.com/?p=323</guid>
		<description><![CDATA[I tried to discuss things, that I've missed last time.]]></description>
		<wfw:commentRss>http://blog.eurekalog.com/catching-memory-leaks-redux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to read bug-reports</title>
		<link>http://blog.eurekalog.com/how-to-read-bug-reports/</link>
		<comments>http://blog.eurekalog.com/how-to-read-bug-reports/#comments</comments>
		<pubDate>Tue, 28 Jul 2009 05:31:20 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Delphi]]></category>
		<category><![CDATA[Access Violation]]></category>
		<category><![CDATA[bug reports]]></category>
		<category><![CDATA[EL 6.x]]></category>
		<category><![CDATA[how it works]]></category>
		<category><![CDATA[memory leaks]]></category>
		<category><![CDATA[other tools]]></category>

		<guid isPermaLink="false">http://blog.eurekalog.com/?p=230</guid>
		<description><![CDATA[Well, recently I’ve noticed that there are many people, who have certain difficulties with reading and/or understanding bug-reports. There are many related questions both on support and forums. While it is quite surprising for me, it looks like there is a problem, which need to be solved.]]></description>
		<wfw:commentRss>http://blog.eurekalog.com/how-to-read-bug-reports/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Catching memory leaks</title>
		<link>http://blog.eurekalog.com/catching-memory-leaks/</link>
		<comments>http://blog.eurekalog.com/catching-memory-leaks/#comments</comments>
		<pubDate>Tue, 26 May 2009 20:32:30 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Delphi]]></category>
		<category><![CDATA[Access Violation]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[how it works]]></category>
		<category><![CDATA[memory leaks]]></category>
		<category><![CDATA[other tools]]></category>

		<guid isPermaLink="false">http://blog.eurekalog.com/?p=198</guid>
		<description><![CDATA[Before return to discussion of other ways to catch "bad" pointers - I wanted to talk about memory leaks and tools for its diagnostics. As we'll see later, this topic is very close related to our previous talk.]]></description>
		<wfw:commentRss>http://blog.eurekalog.com/catching-memory-leaks/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>EurekaLog&#8217;s anti-freeze feature</title>
		<link>http://blog.eurekalog.com/eurekalogs-anti-freeze-feature/</link>
		<comments>http://blog.eurekalog.com/eurekalogs-anti-freeze-feature/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 08:00:21 +0000</pubDate>
		<dc:creator>Alex</dc:creator>
				<category><![CDATA[Delphi]]></category>
		<category><![CDATA[additional features]]></category>
		<category><![CDATA[EL 6.x]]></category>
		<category><![CDATA[feature]]></category>
		<category><![CDATA[how it works]]></category>
		<category><![CDATA[memory leaks]]></category>

		<guid isPermaLink="false">http://blog.eurekalog.com/?p=6</guid>
		<description><![CDATA[As you know, EurekaLog is a great tool to catch exceptions in your application. Though there are some cases which you want to consider as "bugs", but there is no exception to catch it! 
For example, consider your application is deadlocking. How about endless cycle which loads CPU core up to 100%? What about do not updating your UI for 10 minutes? Are those issues bugs or not?
Yes, all these cases are bugs in your application. But no exception is raised in such cases - your application simply stops working. Those cases can be very nasty and hard to diagnose, because your application doesn't show any error message and doesn't generate any log files. 

So, how can you catch them? ]]></description>
		<wfw:commentRss>http://blog.eurekalog.com/eurekalogs-anti-freeze-feature/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
