Maybe I&#x27;m unclear on some of the details here, but here goes<p><a href="https:&#x2F;&#x2F;docs.oracle.com&#x2F;javase&#x2F;specs&#x2F;jls&#x2F;se8&#x2F;html&#x2F;jls-12.html#jls-12.5" rel="nofollow">https:&#x2F;&#x2F;docs.oracle.com&#x2F;javase&#x2F;specs&#x2F;jls&#x2F;se8&#x2F;html&#x2F;jls-12.htm...</a><p>&quot;Whenever a new class instance is created, memory space is allocated for it with room for all the instance variables declared in the class type and all the instance variables declared in each superclass of the class type, including all the instance variables that may be hidden (§8.3).&quot;<p>Doesn&#x27;t seem to allow for escape analysis eliminating the object. Plus escape analysis wouldn&#x27;t really save you. These are class instances, you pretty much have to declare them before the scope you use them in, if you&#x27;re using them in the condition of a while loop (which would be the way to use them).<p>I seem to have this experience in practice. If you have a value type and loop over it, creating a &quot;dummy&quot; instance of it outside of the loop, then erase and reset it&#x27;s inner state on every loop iteration is far faster than creating an instance inside the loop. So I don&#x27;t think escape analysis optimizes this case.