Chrome shows multiple black windows when logging is enabled
Reported by
ndrantot...@gmail.com,
Nov 5 2017
|
|||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Steps to reproduce the problem:
1. Open an URL/app in Chrome with "--enable-logging" and "--kiosk" switches/flags set (CHROME_LOG_FILE is also set as environment variable)
2. The page/app is opened but another black windows are opened too
3. The black windows seem to show logs
What is the expected behavior?
No black windows like DOS console should be created ("kiosk" switch set or not)
Log is written in the CHROME_LOG_FILE path set in environment.
What went wrong?
I use Chrome to run a kiosk application. If Chrome creates another windows, it may mask the main one and could disable GPU. A weird thing is it seems not occurring on another version of Windows.
Did this work before? No
Chrome version: 61.0.3163.100 Channel: n/a
OS Version: Windows 10 Enterprise 2015 LTSB
Flash Version:
,
Nov 29 2017
Unable to reproduce this issue on Windows-10 Enterprise using chrome latest stable #62.0.3202.94 by following steps mentioned in the original comment. Observed the kiosk mode is launched with the expected webpage and no black screen is observed. ndrantotiana.rindra@ Could you please confirm are you still observing this issue on chrome latest stable #62.0.3202.94? Thanks!
,
Dec 12 2017
Hello. I'm still having this issue. In fact my app is using WebGL and I think that the WebGL (GPU) log is displayed in the black screen or the Chrome GPU-related process is launched through this black screen. I want to note too that I'm launching Chrome via Java application.
,
May 22 2018
Unable to reproduce the issue on windows 10 enterprise using reported version-61.0.3163.100 & latest stable-66.0.3359.181 as per below steps. 1. Install chrome 2. Launch chrome via terminal with below command chrome.exe www.fb.com --enable-logging --kiosk Observation: ----------- Chrome launched successfully with fb.com page opened in kiosk mode. Please check the issue on latest chrome versions & let us know your update on the same & find the attached screencast for reference. Thanks..!
,
May 22 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 22 2018
Thank you for your test. I have no more Windows Enterprise 2015 LTSB VM at my hand but I will try as soon as I get one. Meanwhile, could you try to test launching Chrome through command line by opening https://playground.babylonjs.com/frame.html#LL5BIQ#0 and clicking on "From walk to run" button instead of fb.com and adding "--v=4" to command line switches? I think the log verbosity and this webpage will force the GPU logging. Thank you in advance.
,
May 23 2018
As per comment #6 we have tested this issue and we are unable to reproduce the issue reported version on 61.0.3163.100 and latest chrome stable 66.0.3359.181 using Win 10 & 7. Attaching Screencast for reference. Steps -------- 1. Launched Chrome through command line with chrome executable path ""chrome.exe https://playground.babylonjs.com/frame.html#LL5BIQ#0 --enable-logging --kiosk"" We are able to see the page with animation. @Reporter: can you please check the issue on latest chrome versions 66.0.3359.181 & let us know.The latest chrome builds can be downloaded from the below URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
May 28 2018
As per comment#7 adding Needs-Feedback label to the issue. Thanks!
,
Nov 9
As there is no update from the reporter since a long time, marking this issue as WontFix. Please feel free to raise a new bug if any issues are observed on the latest Chrome builds. Thanks.. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Nov 6 2017