<p>There have been numerous Java-related blog posts in recent days and I reference and summarize four of them here.</p><p>Creating a Memory Leak</p><p>In the "rather evil post" How to Create a Memory Leak, Ivo Maegi describes and provides code examples of two commons leaks. The first leak covered is related to objects lacking the hashCode()/equals(Object) implementations to be used properly in collections needing them to be correct. The second covered leak is related to the change of handling for String internals in Java 7 Update 6. The second problem is a reminder of the subtle and difficult to diagnose issues that can occur when even minor differences exist between versions of Java used in different environments.</p><p>StringBuffer Was Never a Good Idea</p><p><a href="http://www.javaworld.com/community/?q=node/13365">Keep reading...</a></p>