Logging doesn't work in utility process on Windows |
|||
Issue descriptionIf I use --no-sandbox, logging works when using ServiceUtilityProcessHost. Otherwise, logging doesn't work. This is inconvenient for debugging as we move more services to the utility process.
,
Sep 24
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fe29a58304773b03a59e50af2d64627ff5d31765 commit fe29a58304773b03a59e50af2d64627ff5d31765 Author: Xiaohan Wang <xhwang@chromium.org> Date: Mon Sep 24 17:45:51 2018 sandbox: Allow utility process to access the log file on Windows Currently this is only allowed for renderer and gpu process. This CL also allows it for utility process. Also pass logging switches to the UtilityProcessHost. These switches are already passed in ServiceUtilityProcessHost. Both are using kUtilityProcess process type. Bug: 888088 Change-Id: Ic26b9c9e6ce0c9024fb3ca4c8d352c5a283bef81 Reviewed-on: https://chromium-review.googlesource.com/1239172 Reviewed-by: Will Harris <wfh@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Commit-Queue: Xiaohan Wang <xhwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#593588} [modify] https://crrev.com/fe29a58304773b03a59e50af2d64627ff5d31765/content/browser/utility_process_host.cc [modify] https://crrev.com/fe29a58304773b03a59e50af2d64627ff5d31765/services/service_manager/sandbox/win/sandbox_win.cc
,
Sep 24
,
Dec 9
Issue 865472 has been merged into this issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by xhw...@chromium.org
, Sep 21