New issue
Advanced search Search tips

Issue 689736 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
EstimatedDays: ----
NextAction: 2019-07-09
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

console window pops for unsandboxed utility process

Project Member Reported by wfh@chromium.org, Feb 7 2017

Issue description

Chrome Version: 58.0.3006.0 cb16ddfff8577ff
OS: Win 10

What steps will reproduce the problem?
(1) Start chrome with --enable-logging=stderr --v > log.txt 2>&1
(2) Wait
(3)

What is the expected result?

No console window pops

What happens instead?

A console window appears and disappears. it appears the command line of the process is:

chrome.exe --type=utility --lang=en-US --no-sandbox --user-data-dir="d:\src\temp" --enable-logging=stderr --v --service-request-channel-token=03431BA27821BF3E0DAFF0551001D99D --mojo-platform-channel-handle=5976 /prefetch:8

This then spawns a conhost.exe:

C:\Windows\system32\conhost.exe 0xffffffff -ForceV1

I'm not sure why this would be happening.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Comment 1 by wfh@chromium.org, Feb 8 2017

would guess maybe having --logging on for an unsandboxed process does some sort of console output?
Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.

Sign in to add a comment