<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: DllHost Memory Leak</title>
	<atom:link href="http://www.thejackol.com/2005/07/06/dllhost-memory-leak/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thejackol.com/2005/07/06/dllhost-memory-leak/</link>
	<description>01100010 01101100 01100101 01101000</description>
	<lastBuildDate>Tue, 07 Feb 2012 21:10:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Memory leaking in Contributor &#171; ykud</title>
		<link>http://www.thejackol.com/2005/07/06/dllhost-memory-leak/comment-page-1/#comment-35562</link>
		<dc:creator>Memory leaking in Contributor &#171; ykud</dc:creator>
		<pubDate>Tue, 14 Nov 2006 10:27:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/?p=157#comment-35562</guid>
		<description>[...] A vile and mean way of killing dllhost.exe, after it reached some limit. That is done easily, as noted here, for example. That can lead to some trouble, though, for example if dllhost is killed in the middle of reconcile process. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] A vile and mean way of killing dllhost.exe, after it reached some limit. That is done easily, as noted here, for example. That can lead to some trouble, though, for example if dllhost is killed in the middle of reconcile process. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dk</title>
		<link>http://www.thejackol.com/2005/07/06/dllhost-memory-leak/comment-page-1/#comment-17089</link>
		<dc:creator>dk</dc:creator>
		<pubDate>Mon, 07 Nov 2005 12:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejackol.com/?p=157#comment-17089</guid>
		<description>Evidently this is a known Microsoft issue.  MS made a &quot;fix&quot; for this, it is a file called IIS5recycle.  use that search term on MS&#039;s site and you will find it.  It runs as a service and allows you control conditions to kill dllhost, such as memory thershold, page requests, time, timer, etc.  It runs as a service and will also do logging.  It is funny how MS acknowledges a memory leak problem, but instead of fixing the cause, the build a band-aid for the symptom.

Be warned: I believe one of MS&#039;s latest patches breaks the IIS5recycle.</description>
		<content:encoded><![CDATA[<p>Evidently this is a known Microsoft issue.  MS made a &#8220;fix&#8221; for this, it is a file called IIS5recycle.  use that search term on MS&#8217;s site and you will find it.  It runs as a service and allows you control conditions to kill dllhost, such as memory thershold, page requests, time, timer, etc.  It runs as a service and will also do logging.  It is funny how MS acknowledges a memory leak problem, but instead of fixing the cause, the build a band-aid for the symptom.</p>
<p>Be warned: I believe one of MS&#8217;s latest patches breaks the IIS5recycle.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

