Issue metadata
Sign in to add a comment
|
Very slow networking of chromium in headless mode when there is a active virtual network adapter on the computer
Reported by
fmonch...@vigiteck.com,
Jan 24 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3312.0 Safari/537.36 Steps to reproduce the problem: 1. Install a local hypervisor (ex: Virtual Box, Vmware). This installation will create virtual network adapter. 2. Execute : "chrome --headless --disable-gpu --screenshot https://www.nytimes.com/" It takes approx. 4 minutes to load the page. 3. Desactivate all the virtual network adapter. Execute the same line. It takes approx 5 seconds to load the page. What is the expected behavior? Chromium to have the same network behavior with or without virtual network adapter installed on the computer in headless mode. What went wrong? It took 4 minutes to load the page. It can be reproduce on many web sites, not only nytimes.com Did this work before? N/A Does this work in other browsers? N/A Chrome version: 65.0.3312.0 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This behavior (slow networking) seems only to happen in headless mode when there is a active virtual network adapter on the computer.
,
Jan 26 2018
What happens while Chrome is slow to load? Do you see a network load status? (If so, what is it). Are other pages interactive? For instance can you navigate to "chrome://version" ? Do you have proxy auto-detect enabled? Does disabling it make any difference?
,
Jan 29 2018
Hi, Thanks for your feedback. Your comments give me some points to investigate. The problem is with the proxy settings. I'm not sure to understand why because I did not have a proxy and didn't configure chrome to use a proxy... Adding the option --proxy-server="direct://" solve the problem (I took this from https://www.chromium.org/developers/design-documents/network-settings) : chrome --headless --disable-gpu --proxy-server="direct://" --screenshot https://www.nytimes.com/ If use with puppeteer, you have to omit the double quotes for "direct://" : const browser = await puppeteer.launch({headless: true, args: ['--proxy-server=direct://']});
,
Jan 29 2018
Thank you for providing more feedback. Adding requester "eroman@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 29 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susanjun...@techmahindra.com
, Jan 24 2018