Repository: puppeteer
Issue: [Bug]: Browser crashes when a navigational request is aborted using --single-process flag
Labels: bug,upstream,confirmed,P3

### Minimal, reproducible example

```TypeScript
import puppeteer from 'puppeteer';

const args = [
  '--allow-pre-commit-input',
  '--disable-background-networking',
  '--disable-background-timer-throttling',
  '--disable-backgrounding-occluded-windows',
  '--disable-breakpad',
  '--disable-client-side-phishing-detection',
  '--disable-component-extensions-with-background-pages',
  '--disable-component-update',
  '--disable-default-apps',
  '--disable-dev-shm-usage',
  '--disable-extensions',
  '--disable-hang-monitor',
  '--disable-ipc-flooding-protection',
  '--disable-popup-blocking',
  '--disable-prompt-on-repost',
  '--disable-renderer-backgrounding',
  '--disable-sync',
  '--enable-automation',
  '--enable-blink-features=IdleDetection',
  '--export-tagged-pdf',
  '--force-color-profile=srgb',
  '--metrics-recording-only',
  '--no-first-run',
  '--password-store=basic',
  '--use-mock-keychain',
  '--disable-domain-reliability',
  '--disable-print-preview',
  '--disable-speech-api',
  '--disk-cache-size=33554432',
  '--mute-audio',
  '--no-default-browser-check',
  '--no-pings',
  '--single-process',
  '--font-render-hinting=none',
  '--disable-features=Translate,BackForwardCache,AcceptCHFrame,MediaRouter,OptimizationHints,AudioServiceOutOfProcess,IsolateOrigins,site-per-process',
  '--enable-features=NetworkServiceInProcess2,SharedArrayBuffer',
  '--hide-scrollbars',
  '--ignore-gpu-blocklist',
  '--in-process-gpu',
  '--disable-webgl',
  '--allow-running-insecure-content',
  '--disable-setuid-sandbox',
  '--disable-site-isolation-trials',
  '--disable-web-security',
  '--no-sandbox',
  '--no-zygote',
  "--headless='chrome-headless-shell'",
  "--disk-cache-size=268435456",
  "--window-size=1366,4608",
  "--ignore-certificate-errors",
  "--user-data-dir=/tmp/chrome-user-data"
]

(async () => {
  // Launch the browser and open a new blank page
  const browser = await puppeteer.launch({
    args:              args,
    defaultViewport:   { width: 1366, height: 4608 },
    headless:          "chrome-headless-shell",
    dumpio:            true
  });

  const page = await browser.newPage();

  // Enable request interceptions
  await page.setRequestInterception(true);

  // do not load images and fonts
  await page.on("request", (request) => {
    if (request.isInterceptResolutionHandled()) return;

    if (request.isNavigationRequest())
      request.abort("blockedbyclient");
    else
      request.continue();
  });

  // Navigate the page to a URL
  await page.goto('https://developer.chrome.com/');

  await browser.close();
})();
```


### Error string

bad_message.cc(29)] Terminating renderer for bad IPC message, reason 205

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

This upstream bug happens when the `single-process` option is set. In this case, when a navigational request is being aborted the renderer is being killed, which leads to browsed death. This shouldn't happen in a single process mode I believe.

I was able to reproduce this with response interceptions as well https://stackoverflow.com/a/78263262/4846702

More details about what is happening https://issues.chromium.org/issues/40058380

### Expectation

The browser should keep running when a navigational request is aborted.

### Reality

The browser process dies along with the renderer.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.4.1

### Node version

20.11.1

### Package manager

npm

### Package manager version

10.2.4

### Operating system

Linux