New issue
Advanced search Search tips

Issue 882351 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
ossu@chromium.org
maxmorin@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Official builds sometimes crash on LOG(ERROR) with --enable-logging

Project Member Reported by maxmorin@chromium.org, Sep 10 
In issue 823970, we investigated an issue with LOG(ERROR) crashing. It seems like stderr is either closed or wasn't opened to begin with. The crash seems to happen in a variety of processes (see go/isattycrashesinbrowser for browser crashes).

This was also investigated in
 Issue 698307  (closed without conclusive fix),
Issue 782502 (blamed on kaspersky dlls which are not present here),
Issue 629779 (shrug won'tfix),
Issue 625838 (no activity whatsoever),
Issue 625101 (won'tfix),
Issue 787515 (open, seems to be the same thing? Discussions about sandboxing interfering with fwrite somehow.).

Oskar: feel free to mention anything I missed.

Comment 1 by ossu@chromium.org, Sep 10 

For what it's worth, it's been replicated with --enable-logging on an official build.

I tried to replicate it on a local build (non-official) by commenting out a couple of seemingly relevant lines that wouldn't be run in an official build:
- calls to RouteStdioToConsole()
- calls to SetStdoutHandle() and SetStderrHandle() in SandboxWin.
This did not help me reproduce the problem.

As a side note: if I pipe the output of Chrome into NUL, it just freezes.
►

Sign in to add a comment