Cannot start graphical Chrome on macOS if Headless was launched first
Reported by
atomicra...@gmail.com,
Dec 14 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0 Steps to reproduce the problem: 1. Launch Headless Chrome (I'm doing this via Karma, but it seems to be the same no matter how it's launched) 2. Attempt to launch Chrome using Spotlight, the Dock, or any other means What is the expected behavior? A standard graphical Chrome session starts and appears What went wrong? Graphical Chrome won't start until Headless is killed. Headless can be launched if graphical Chrome was started first, but not the other way around. Did this work before? N/A Chrome version: 63.0.3239.84 (Official Build) (64-bit) Channel: stable OS Version: OS X 10.13 Flash Version: Shockwave Flash 28.0 r0
,
Dec 15 2017
Thanks for the report, I can confirm this happens, I'm guessing spotlight check if the binary is running before running the same instance, and think that headless is in fact running. Running from command line works though. This seems like low priority to fix though. A work around is running from command line or running headless from a different Chrome binary |
||
►
Sign in to add a comment |
||
Comment 1 by chenwilliam@chromium.org
, Dec 15 2017