Some pages not fully loading when setRequestInterception set to true

• Puppeteer version: 1.14.0
• Platform / OS version: Windows 10
• Node.js version: 10.15.3

Complete code to reproduce the problem:

const puppeteer = require('puppeteer');

(async () => {
    const browser = await puppeteer.launch({ 
        headless: false, 
        devtools: false
    });
    const page = await browser.newPage();
    await page.setViewport({ width: 1920, height: 1080 });
    await page.setRequestInterception(true);
    page.on('request', request => {
        request.continue();
    });

    await page.goto('http://123tvnow.com/watch/cbs/',)
    .catch((e) => {console.log(e)})
    // await browser.close();
})();

If setRequestInterception is set to true, the page never fully loads event thou all requests seem to be handled. Some sub-pages of the included example website do load, like: http://123tvnow.com/watch/espn If you enable dev tools you’ll need to deactivate breakpoints and resume. It’s just the way site owner coded it.

After 30 seconds a TimeoutError error will be caught. I would like to understand why this is happening? It is especially confusing because some sub-pages load without a problem so I didn’t expect the xhr streaming files be an issue or .ttf or something similar.

[Yokutto]

Hello everyone, I faced this issue updating puppeteer 1.12 to 1.15 without update Chrome version (NOT CHROMIUM) and in my case the page never loads and always show a blank page without any error.

To fix this, go to release notes, here you can see the required Chromium version in order to use puppeteer correctly, in this case, you need to update to: Chromium 75.0.3765.0. (puppeteer 1.15)

If you use Google Chrome (not chromium), you will need to wait until Jun 4 for official stable release (v75), or install the version in beta (unstable)

[jazoom]

Doesn’t work for me in the stated versions and I let Puppeteer download the version of Chromium automatically.