Programming

Lewis looks at how to walk a file tree in Java with the walkFileTree() method and the FileVIsitor interface.

In the final part of this series on memory leaks in Java, Lewis takes a look at the JDK Flight Recorder and JDK Mission Control tools. Together these create a complete tool chain to continuously collect detailed runtime information.

Now that you know about some of the causes of memory leaks in your Java program, Lewis takes a quick look at profilers and other tools that can help you, in particular VisualVM and JConsole.

Lewis looks at how you can use the verbose output from the garbage collector to find memory leaks in your Java program.

In part 4 of this series on memory leaks in Java, Lewis looks at how incorrect or missing equals() and hashCode() methods can cause memory leaks.

Lewis continues his series on how to avoid memory leaks in Java. This week he looks at the effect of string interning on memory.

Lewis provides some more examples of code that can lead to memory leaks, in particular how to use the static modifier.

Computer memory is a vital and scarce resource. So programmers must manage memory with care. Memory leaks can block file resources, reduce memory availability and degrade system performance. Lewis looks at some of the causes of memory leaks in Java.

The Principle of Least Surprise (POLS), also known as the Principle of Least Astonishment (POLA), is a design guideline for both software and user interfaces. It says that every component in a system should behave in a way that most users expect it to behave, and therefore not surprise or astonish them.

Lewis looks at how to schedule tasks to run regularly, using the ScheduledThreadPoolExecutor. This is the last part of our series on threads and multithreading in Java.