<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kirk Pepperdine on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/kirk-pepperdine/</link><description>Articles written by Kirk Pepperdine on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Jul 2026 13:49:39 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/kirk-pepperdine/index.xml" rel="self" type="application/rss+xml"/><item><title>Nulling Out References Won't Help Your Garbage Collector</title><link>https://foojayio.github.io/website/today/nulling-out-references-wont-help-your-garbage-collector/</link><pubDate>Thu, 09 Jul 2026 13:49:39 +0000</pubDate><guid>https://foojayio.github.io/website/today/nulling-out-references-wont-help-your-garbage-collector/</guid><description>&lt;p&gt;One of the misconceptions that I continuously run into is that nulling out references in Java helps garbage collection.&lt;/p&gt;
&lt;p&gt;This attitude is particularly prevalent from those developers used to C/C++ where &lt;code&gt;delete ptr&lt;/code&gt; becomes &lt;code&gt;ref = null&lt;/code&gt;. To be fair, it&amp;rsquo;s a reasonable thing to believe.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s also wrong, and the way it&amp;rsquo;s wrong tells you most of what&amp;rsquo;s worth knowing about how a tracing collector actually works.&lt;/p&gt;
&lt;p&gt;That is, the vast majority of data allocated in a tracing garbage collected runtime becomes collectable as soon as a variable falls out of scope.&lt;/p&gt;</description></item></channel></rss>