Moving both profile_directory and browser_directory to possible_browser sgtm; those two sound like things that _should_ be possible to compute before the browser is started.
> ChromeOS: Some dynamic logic to get browser directory based on ChromeProcess
This could be a deal killer. +achuith, is it possible to figure out the browser_directory _before_ starting the browser?
I'm actually not quite sure how this works now. Today we FlushSystemCache for browser_directory _before_ starting the browser and, at that time, browser_directory returns None?
I also noticed that on Android profile_directory does not work (and it was indeed never called because of comment #8). I tried to take it from browser_options instead of _backend_settings, but it did not immediately help. Did not look further yet.
Finding profile directory and cache directory is pretty important for benchmarking "coldish" start on Android.
possible_browser sounds good to me. If we cannot determine profile_directory without starting a browser (on chromeos), we could potentially start the browser lazily once for shared_page_state and memoize the value?
Juan: this bug is done enough to the point that it no longer blocks issue 784319 . The rest left is deprecate the credential_paths & credential fields.
Comment 1 by nedngu...@google.com
, Nov 21 2017