What are the primary dangers of using a broad `catch` block (e.g., `catch (Exception e)` or `catch (Throwable t)`)?

Responsive Ad Header

Question

Grade: Education Subject: Support
What are the primary dangers of using a broad `catch` block (e.g., `catch (Exception e)` or `catch (Throwable t)`)?
Asked by:
115 Viewed 115 Answers
Responsive Ad After Question

Answer (115)

Best Answer
(450)
Broad `catch` blocks mask specific errors, making debugging significantly harder. They can hide critical issues like `NullPointerException` or `OutOfMemoryError`, preventing you from addressing the root cause. They also prevent more specific error handling logic from being applied, potentially leading to unexpected behavior and system instability. It's like putting a blanket over a fever – you're suppressing the symptom, not curing the disease.