Should try‑catch Be Inside or Outside a for Loop? Pros, Cons, and Performance

Introduction

During an interview a candidate was asked about the effect of placing a try‑catch block inside or outside a for loop, a basic but important question.

Usage Scenarios

The position of try‑catch depends on business requirements: placing it outside the loop stops the loop when an exception occurs, while placing it inside allows the loop to continue.

1. try‑catch outside the for loop

Code example:

public static void tryOutside() {
    try {
        for (int count = 1; count <= 5; count++) {
            if (count == 3) {
                // deliberately cause exception
                int num = 1 / 0;
            } else {
                System.out.println("count:" + count + " business normal execution");
            }
        }
    } catch (Exception e) {
        System.out.println("try catch outside for: exception occurred, loop terminated");
    }
}

Result:

When the try‑catch is outside the for loop, an exception terminates the loop.

2. try‑catch inside the for loop

Code example:

public static void tryInside() {
    for (int count = 1; count <= 5; count++) {
        try {
            if (count == 3) {
                // deliberately cause exception
                int num = 1 / 0;
            } else {
                System.out.println("count:" + count + " business normal execution");
            }
        } catch (Exception e) {
            System.out.println("try catch inside for: exception caught, loop continues");
        }
    }
}

Result:

When the try‑catch is inside the for loop, the exception is caught and the loop continues.

Performance

Time cost is essentially the same when no exception occurs; memory usage is also similar. However, if many iterations throw exceptions, memory consumption can increase because each catch creates an exception object.

Example of measuring memory:

Runtime runtime = Runtime.getRuntime();
long memory = runtime.freeMemory();

Placing try‑catch inside the loop does not terminate the loop, so large numbers of exceptions may lead to higher memory usage.

Personal View

If you need the loop to stop on an exception, put the try‑catch outside; otherwise keep it inside. Avoid performing heavy operations such as database calls inside the loop.