<?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: WTF Bluehost?!</title>
	<atom:link href="http://brickblog.net/2007/12/23/wtf-bluehost/feed" rel="self" type="application/rss+xml" />
	<link>http://brickblog.net/2007/12/23/wtf-bluehost</link>
	<description>Brick blog, intended about Lego, but wound up everything else</description>
	<lastBuildDate>Mon, 09 Jan 2012 11:33:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: kayakermanmike</title>
		<link>http://brickblog.net/2007/12/23/wtf-bluehost/comment-page-1#comment-4263</link>
		<dc:creator>kayakermanmike</dc:creator>
		<pubDate>Tue, 25 Dec 2007 13:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://brickblog.net/2007/12/23/wtf-bluehost/#comment-4263</guid>
		<description>Thanks Dave! I&#039;ll take a look at it when I&#039;m not with family for Christmas.</description>
		<content:encoded><![CDATA[<p>Thanks Dave! I&#8217;ll take a look at it when I&#8217;m not with family for Christmas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://brickblog.net/2007/12/23/wtf-bluehost/comment-page-1#comment-4262</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 24 Dec 2007 19:11:27 +0000</pubDate>
		<guid isPermaLink="false">http://brickblog.net/2007/12/23/wtf-bluehost/#comment-4262</guid>
		<description>Hmm...but if they have a hard cap of memory per site it could mean the memory leak is on your side?  But the entire point of newer scripting languages is that garbage collection is done server-side.  

My PHP book is sitting on the shelf at work, but it looks like to manually free up the memory you can use the unset(); function for your variables and session_unset();
session_destroy(); for any session variables.

Toss a function at the end of your scripts and see if the problem goes away.  That&#039;s Dave&#039;s troubleshooting with minimal knowledge of PHP and not looking at your code at all.  Use that information to calibrate the grain of salt you want to take the advice with ;-)</description>
		<content:encoded><![CDATA[<p>Hmm&#8230;but if they have a hard cap of memory per site it could mean the memory leak is on your side?  But the entire point of newer scripting languages is that garbage collection is done server-side.  </p>
<p>My PHP book is sitting on the shelf at work, but it looks like to manually free up the memory you can use the unset(); function for your variables and session_unset();<br />
session_destroy(); for any session variables.</p>
<p>Toss a function at the end of your scripts and see if the problem goes away.  That&#8217;s Dave&#8217;s troubleshooting with minimal knowledge of PHP and not looking at your code at all.  Use that information to calibrate the grain of salt you want to take the advice with ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://brickblog.net/2007/12/23/wtf-bluehost/comment-page-1#comment-4261</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 24 Dec 2007 18:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://brickblog.net/2007/12/23/wtf-bluehost/#comment-4261</guid>
		<description>I noticed that.  I&#039;m assuming you&#039;re on a shared server, I have to wonder if someone on the same server wrote some code with a memory leak in it.</description>
		<content:encoded><![CDATA[<p>I noticed that.  I&#8217;m assuming you&#8217;re on a shared server, I have to wonder if someone on the same server wrote some code with a memory leak in it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

