Headless mode on Windows 7 causes timeout, never completes

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 1.3.0
• Platform / OS version: Windows 7 x64
• URLs (if applicable):
• Node.js version: 8.9.4

What steps will reproduce the problem?

const puppeteer = require('puppeteer')
const devices = require('puppeteer/DeviceDescriptors')

const captureScreenshot = async () => {
  const browser = await puppeteer.launch({headless:true})
  const page = await browser.newPage()
  await page.goto('https://www.google.com/')
  await page.screenshot({path: 'screenshot.png', fullPage: true})
  await browser.close()
}

captureScreenshot()

1. npm install puppeteer
2. node index.js

What is the expected result? Script runs and outputs screenshot.png into working directory.

What happens instead? Script runs for a long time until it produces timeout warnings.

(node:4492) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejec
tion id: 1): Error: Navigation Timeout Exceeded: 30000ms exceeded
(node:4492) [DEP0018] DeprecationWarning: Unhandled promise rejections are depre
cated. In the future, promise rejections that are not handled will terminate the
 Node.js process with a non-zero exit code.

If puppeteer.launch option “headless” is set to false, same script delivers expected result in about 5 seconds.

Capturing screenshot from http://info.cern.ch/ works in headless mode, so issue might be related to complexity of the page.

[TheCloudlessSky]

Does this work?

const browser = await puppeteer.launch({
  headless: true,
  args: [
    '--proxy-server="direct://"',
    '--proxy-bypass-list=*'
  ]
});

[TheCloudlessSky]

@joshas It shouldn’t be… but I’ve ran into serious problems with this too. I’ve added this comment to my code for those arguments:

    // Headless mode sometimes ignores the default OS proxy (by default none). This causes some
    // machines to take ~2 seconds per-request and significantly inflate the test suite run
    // time by more than 10x. This was also sometimes a problem when running PhantomJS. The
    // suggested workaround is to explicitly bypass all proxies:
    // https://github.com/Codeception/CodeceptJS/issues/561#issuecomment-373666779
    // https://peter.sh/experiments/chromium-command-line-switches/#proxy-server
    // https://peter.sh/experiments/chromium-command-line-switches/#proxy-bypass-list