Error Handling & Diagnostics in Web Workers

Technical Deep Dive & Specifications

The Hierarchy of Web Worker Errors

+---------------------------------------------------------------------------------------------------+
|                                  WORKER ERROR TAXONOMY                                            |
+---------------------------------------------------------------------------------------------------+

   1. Script Loading Errors (Fetch / SOP / MIME Mismatch)
      └── Fired on: `worker.onerror` on the Main Thread (Worker fails to initialize)

   2. Runtime Exceptions (`throw`, `TypeError`, `ReferenceError`)
      ├── Handled in Worker: `self.onerror` / `self.addEventListener('error')`
      └── Bubbles to Main:   `worker.onerror` / `worker.addEventListener('error')`

   3. Message Deserialization Errors (`messageerror`)
      ├── Fired when: Incoming message payload cannot be deserialized by Structured Clone
      └── Handled via: `worker.onmessageerror` / `self.onmessageerror`

   4. Unhandled Promise Rejections
      └── Handled in Worker: `self.addEventListener('unhandledrejection')`

The ErrorEvent Interface

When an unhandled exception occurs in a worker, an ErrorEvent is dispatched with the following properties:

worker.onerror = function(event) {
  console.error(`Worker error in ${event.filename} at line ${event.lineno}:${event.colno}`);
  console.error(`Message: ${event.message}`);
  
  // Prevent error from bubbling up as an unhandled console exception
  event.preventDefault();
};

Error Event Bubbling & preventDefault()

According to the WHATWG HTML Living Standard:

1. An unhandled exception in a worker first triggers self.onerror inside the worker scope.
2. If self.onerror does not prevent default, an ErrorEvent bubbles across the thread boundary to the parent Worker object's onerror handler.
3. If the main thread's worker.onerror also does not call event.preventDefault(), the browser logs the error as an Unhandled Exception in the browser developer console.

The messageerror Event

The messageerror event is distinct from onerror:

• It fires when an incoming message cannot be parsed or deserialized into a valid object.
• For instance, if data transmission was corrupted, or memory constraints prevented materializing a cloned object graph.

worker.addEventListener('messageerror', (event) => {
  console.error('Failed to deserialize incoming message payload from worker!');
});

💻 Interactive Code Playground

Below is a complete Worker Error Diagnostics Laboratory & Self-Healing Supervisor. You can deliberately trigger different classes of errors and watch the supervisor intercept and restart the worker.

Starter Code

Line-by-Line Code Breakdown

• Lines 63–109: The ResilientWorkerSupervisor class wraps worker creation, error listening, and automatic thread rejuvenation.
• Lines 82–99 (this.worker.onerror = (event) => { ... }): Intercepts the bubbling ErrorEvent, extracts event.message and event.lineno, and calls event.preventDefault() to suppress unhandled browser error spam.
• Line 98: Automatically calls this.spawn() to boot a fresh worker instance after a crash.
• Lines 118–122 (unhandledrejection): Worker-level listener that traps unhandled Promise rejections and rethrows them as standard errors so worker.onerror can capture them.
• Lines 129–131: Deliberately executes null.nonExistentMethod(), triggering an instantaneous TypeError.

Expected Browser Render Output

🛠️ Worker Error Diagnostics & Supervisor
Trigger unhandled exceptions and observe supervisor error interception and thread rebooting.

Supervisor Status: [ Healthy (Worker Active) ]
Crash & Restart Count: 1

[ Button: 1. Run Safe Task ] [ Button: 2. Trigger Synchronous Exception ] [ Button: 3. Trigger Async Rejection ]

Supervisor Diagnostic Telemetry Log:
[02:20:00] 🚀 Spawned fresh SupervisedWorker thread.
[02:20:02] ⚡ Triggering synchronous TypeError in worker...
[02:20:02] 💥 UNCAUGHT WORKER ERROR DETECTED!
[02:20:02]    Message:  Uncaught TypeError: Cannot read properties of null
[02:20:02]    Location: Line 15, Col 15
[02:20:03] 🔄 Supervisor auto-rebooting worker thread...
[02:20:03] 🚀 Spawned fresh SupervisedWorker thread.