<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 20 Jun 2013 02:11:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Derick Rethans' Blog: Collecting Garbage: Cleaning Up]]></title>
      <guid>http://www.phpdeveloper.org/news/15086</guid>
      <link>http://www.phpdeveloper.org/news/15086</link>
      <description><![CDATA[<p>
<i>Derick Rethans</i> has continued his series on garbage collection in the PHP internals with <a href="http://derickrethans.nl/collecting-garbage-cleaning-up.html">this second post</a> of the series with a special look at circular references. You can find the first part <a href="http://phpdeveloper.org/news/15049">here</a>.
</p>
<blockquote>
In this second part of the three part column on the new garbage collecting mechanism in PHP 5.3, we'll dive into a solution to the problem with circular references. If we look quickly back, we found that by using code like the [first example], an in-request memory leak is created.
</blockquote>
<p>
He goes on to briefly describe the synchronous algorithm (including a few more helpful graphs to show the flow) and how that has worked its way into the PHP garbage collection methods. He also points out that this collection can be turned off and on via the <a href="http://php.net/gc_enable">gc_enable</a> and <a href="http://php.net/gc_disable">gc_disable</a> functions. Keep an eye out for the next part of the series where he gets into more detail on how this is all integrated into PHP.
</p>]]></description>
      <pubDate>Tue, 07 Sep 2010 09:56:25 -0500</pubDate>
    </item>
  </channel>
</rss>
