Finally Block Execution Without Catch

Direct Answer

A finally block normally runs when control leaves its try, whether by normal completion, return, or exception propagation. It is not an absolute guarantee: the JVM or process can terminate, the machine can fail, or control may never leave the try. If finally returns or throws, it can discard an earlier return or exception, which is why cleanup should use try-with-resources where possible.

Code Example

public class FinallyDemo {
    int withReturn() {
        try {
            return 1;                 // value computed...
        } finally {
            System.out.println("runs before the method returns");
        }
    }

    void uncaught() {
        try {
            throw new RuntimeException("boom");  // no catch here
        } finally {
            System.out.println("still runs, THEN boom propagates");
        }
    }

    void exits() {
        try {
            System.exit(0);           // JVM stops immediately
        } finally {
            System.out.println("NEVER prints");
        }
    }
}

Common Mistakes & Pitfalls

• Assuming finally needs a catch. It runs even with zero catch blocks — the exception just propagates afterward.
• Throwing from finally. A new exception there replaces the original try exception, destroying the real diagnostic info.
• return inside finally. It silently overrides the try/catch return value — a classic interview gotcha.
• Expecting it after System.exit(). That's the one normal case where finally is skipped.