Currently, there are some cases when session_manager prints the following to the logs:
INFO session_manager: [INFO:browser_job.cc(164)] Terminating process:
(with nothing after ":")
This makes it harder to investigate bugreports where the reason why the browser was killed is unclear - e.g. issue 777532.
We should investigate whether that logging can be enhanced - ideally, so that the message details are always non-empty.
Comment 1 by derat@chromium.org
, Dec 19 2017Status: Started (was: Available)