Handling runtime errors in React - Performance & Optimization

Performance: Handling runtime errors

MEDIUM IMPACT

This affects user experience responsiveness and visual stability by preventing crashes and layout shifts caused by unhandled errors.

Displaying UI without crashing when a runtime error occurs

React

import React from 'react';

class ErrorBoundary extends React.Component {
  constructor(props) {
    super(props);
    this.state = { hasError: false };
  }

  static getDerivedStateFromError(error) {
    return { hasError: true };
  }

  componentDidCatch(error, errorInfo) {
    // log the error
  }

  render() {
    if (this.state.hasError) {
      return <div role="alert">Something went wrong.</div>;
    }
    return this.props.children;
  }
}

function RiskyChild() {
  const data = JSON.parse('invalid json');
  return <div>{data.name}</div>;
}

function MyComponent() {
  return (
    <ErrorBoundary>
      <RiskyChild />
    </ErrorBoundary>
  );
}

Catches errors before they crash the UI, rendering fallback content and preventing layout shifts.

📈 Performance GainAvoids re-render blocking and CLS; improves INP by keeping UI responsive.

Displaying UI without crashing when a runtime error occurs

React

function MyComponent() {
  const data = JSON.parse('invalid json');
  return <div>{data.name}</div>;
}

No error handling causes the entire component to crash, breaking the UI and causing layout shifts.

📉 Performance CostBlocks rendering until error occurs; causes CLS due to sudden UI disappearance.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
No error handling	Component unmounts abruptly	Multiple reflows due to layout shifts	High paint cost from UI flicker	[X] Bad
Error boundary with fallback UI	Stable DOM with fallback nodes	Single reflow for fallback render	Low paint cost, smooth UI	[OK] Good

Rendering Pipeline

Runtime errors interrupt the rendering pipeline causing React to unmount components abruptly, triggering layout shifts and blocking interaction until recovery.

→JavaScript Execution

→Layout

→Paint

→Composite

⚠️ BottleneckJavaScript Execution when errors are unhandled

Core Web Vital Affected

INP, CLS

This affects user experience responsiveness and visual stability by preventing crashes and layout shifts caused by unhandled errors.

Optimization Tips

1Always use error boundaries to catch runtime errors in React components.

2Render fallback UI to avoid layout shifts and keep the interface stable.

3Avoid letting errors crash the entire component tree to maintain responsiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of using error boundaries in React?

A They prevent the entire UI from crashing and reduce layout shifts.

B They increase bundle size but improve loading speed.

C They delay JavaScript execution to improve paint time.

D They eliminate all runtime errors automatically.

DevTools: Performance

How to check: Record a session while triggering an error in the app. Look for long tasks or sudden drops in frame rate.

What to look for: Check for layout shifts in the Experience section and JavaScript errors in the console that cause UI crashes.

Practice

1. What is the main purpose of an error boundary in React?

easy

A. To catch runtime errors in child components and display a fallback UI

B. To improve the performance of React components

C. To handle user input validation

D. To manage component state more efficiently

Solution

1. Step 1: Understand error boundaries role

   Error boundaries catch errors during rendering, lifecycle methods, and constructors of child components.

2. Step 2: Identify their main use

   They prevent the entire app from crashing by showing a fallback UI instead of the broken component.

3. Final Answer:

   To catch runtime errors in child components and display a fallback UI -> Option A

4. Quick Check:

   Error boundaries catch errors = D [OK]

Hint: Error boundaries catch errors and show fallback UI [OK]

Common Mistakes:

• Thinking error boundaries improve performance
• Confusing error boundaries with input validation
• Assuming error boundaries manage state

2. Which of the following is the correct way to define an error boundary component in React?

easy

A. A class component implementing componentDidCatch and getDerivedStateFromError

B. A functional component using useErrorBoundary hook

C. A functional component with try/catch inside render

D. A class component using componentWillCatch lifecycle method

Solution

1. Step 1: Recall error boundary requirements

   Error boundaries must be class components that implement static getDerivedStateFromError and componentDidCatch methods.

2. Step 2: Check options for correct lifecycle methods

   Only A class component implementing componentDidCatch and getDerivedStateFromError correctly names these methods; componentWillCatch does not exist and hooks for error boundaries are not standard.

3. Final Answer:

   A class component implementing componentDidCatch and getDerivedStateFromError -> Option A

4. Quick Check:

   Error boundaries require class + lifecycle methods = A [OK]

Hint: Error boundaries are class components with componentDidCatch [OK]

Common Mistakes:

• Using functional components for error boundaries
• Using non-existent lifecycle methods
• Trying to catch errors inside render with try/catch

3. Given this error boundary component, what will be rendered if a child component throws an error during rendering?

class ErrorBoundary extends React.Component {
  constructor(props) {
    super(props);
    this.state = { hasError: false };
  }
  static getDerivedStateFromError(error) {
    return { hasError: true };
  }
  componentDidCatch(error, info) {
    console.log('Error caught:', error);
  }
  render() {
    if (this.state.hasError) {
      return <h1>Something went wrong.</h1>;
    }
    return this.props.children;
  }
}

medium

A. The child component will render normally

B. An error message 'Something went wrong.' will be displayed

C. The app will crash with an uncaught error

D. Nothing will render because of infinite loop

Solution

1. Step 1: Understand error boundary state update

   When an error occurs, getDerivedStateFromError sets hasError to true, triggering fallback UI.

2. Step 2: Check render output on error

   If hasError is true, render returns <h1>Something went wrong.</h1> instead of children.

3. Final Answer:

   An error message 'Something went wrong.' will be displayed -> Option B

4. Quick Check:

   Error caught triggers fallback UI = C [OK]

Hint: Error sets state to show fallback UI message [OK]

Common Mistakes:

• Expecting child to render despite error
• Thinking app crashes without error boundary
• Assuming infinite loop occurs

4. Identify the error in this error boundary implementation:

class MyErrorBoundary extends React.Component {
  state = { error: null };
  componentDidCatch(error, info) {
    this.setState({ error });
  }
  render() {
    if (this.state.error) {
      return <div>Error occurred</div>;
    }
    return this.props.children;
  }
}

medium

A. State should be initialized in constructor, not as class field

B. Using setState inside componentDidCatch causes infinite loop

C. Missing static getDerivedStateFromError method

D. Error boundary must be a functional component

Solution

1. Step 1: Check error boundary lifecycle methods

   To update state on error, static getDerivedStateFromError must be implemented to update state before render.

2. Step 2: Analyze componentDidCatch usage

   componentDidCatch is for side effects like logging, not for state updates; setState here can cause issues.

3. Final Answer:

   Missing static getDerivedStateFromError method -> Option C

4. Quick Check:

   State update on error requires getDerivedStateFromError = A [OK]

Hint: Use getDerivedStateFromError to update state on error [OK]

Common Mistakes:

• Updating state only in componentDidCatch
• Thinking class fields can't hold state
• Believing error boundaries can be functional components

5. You want to catch errors in multiple nested components but only show one fallback UI at the top level. Which approach is best?

hard

A. Add error boundaries around each nested component separately

B. Use a functional component with useErrorBoundary hook at each level

C. Use try/catch blocks inside each component's render method

D. Wrap the entire app in a single error boundary component

Solution

1. Step 1: Understand error boundary scope

   An error boundary catches errors in its child components and their descendants.

2. Step 2: Choose approach for single fallback UI

   Wrapping the entire app in one error boundary ensures all errors show one fallback UI at top level.

3. Final Answer:

   Wrap the entire app in a single error boundary component -> Option D

4. Quick Check:

   One top-level error boundary = B [OK]

Hint: One top-level error boundary catches all nested errors [OK]

Common Mistakes:

• Adding many error boundaries causing multiple fallback UIs
• Trying to catch errors with try/catch in render
• Using non-existent hooks for error boundaries