Chrome GC logs are not being redirected to a file even though they are visible in terminal
Reported by
czermins...@gmail.com,
Jul 20
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. On MacOS open terminal 2. Run Chrome with flags --js-flags="--trace-gc --trace-gc-verbose" 3. Redirect STDOUT and STDERR to a file What is the expected behavior? A file containing V8 GC logs and errors. What went wrong? STDOUT and STDERR from child processes is not being redirected into the file even though they are visible in a terminal (buffer issue?). Did this work before? No Chrome version: 67.0.3396.99 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: https://stackoverflow.com/questions/51382711/writing-chrome-v8-trace-gc-output-to-a-file-stdout-redirection-does-not-work
,
Jul 25
Able to reproduce the issue on reported chrome version 67.0.3396.99 also on latest chrome 70.0.3501.0 using Mac 10.13.5 and Ubuntu 17.10. NOTE: Not seen logs on Windows -- on both Terminal and File. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Thanks!
,
Jul 26
,
Jul 27
Hi, On Windows Chrome is set as GUI application with no terminal window. If you would like to see Chrome's logs in the terminal you can use EditBin.exe. E. i. EditBin /SUBSYSTEM:CONSOLE chrome.exe
,
Jul 31
Closing according to #4. |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Jul 22