page. setRequestInterception causes network requests to hang/timeout

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 1.20.0
• Platform / OS version: macOS (10.14.5 (18F203))
• URLs (if applicable): https://www.mapbox.com/gallery/#ice-cream
• Node.js version: 10.15.2

What steps will reproduce the problem? Setting request interception causes certain requests to never completely resolve (though the goto method doesn’t seem to mind).

Try the following:

const puppeteer = require('puppeteer');

async function run() {
  let browser = null;

  try {
    browser = await puppeteer.launch();

    const page = await browser.newPage();
    await page.goto('https://www.mapbox.com/gallery/#ice-cream', { waitUntil: 'networkidle0' });
    await page.screenshot({ path : './temp.png' });
  } catch (e) {
    console.error(`Saw error:`, e);
  } finally {
    if (browser) {
      browser.close();
    }
  }
}

run();

This returns a screenshot of:

Now, turn on request interception:

const puppeteer = require('puppeteer');

async function run() {
  let browser = null;

  try {
    browser = await puppeteer.launch();

    const page = await browser.newPage();
    await page.setRequestInterception(true);
    page.on('request', r => r.continue());
    await page.goto('https://www.mapbox.com/gallery/#ice-cream', { waitUntil: 'networkidle0' });
    await page.screenshot({ path : './temp.png' });
  } catch (e) {
    console.error(`Saw error:`, e);
  } finally {
    if (browser) {
      browser.close();
    }
  }
}

run();

This produces the following, as mapping tiles don’t load (they hang)

What is the expected result? All network requests should resolve, when the condition matches

What happens instead? Network requests never resolve completely.

My suspicion is that this has to do with the version of Chromium bundled with pptr, but I haven’t checked prior version just yet.

[h8hawk]

Facing the issue in 2021 as well

[rohitsg]

Enabling await page.setRequestInterception(true); stops futher execution, and removing await page.setRequestInterception(true); will run smoothly. There is issue with await page.setRequestInterception(true);