Issue metadata
Sign in to add a comment
|
ARC doesn't start after r505941 |
||||||||||||||||||||||
Issue descriptionChrome Version: after r505941 OS: Chrome OS Device: caroline What steps will reproduce the problem? (1) Try to boot an Android application. What is the expected result? The app starts. What happens instead? The app doesn't start. Please use labels and text to provide additional information. git-bisect says r505941 (https://chromium-review.googlesource.com/c/chromium/src/+/693037) is the first bad commit. Attached is chrome's log found at the Chromebook's ~/log/chrome For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Oct 4 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hashimoto@chromium.org
, Oct 4 2017In mojo/public/tools/bindings/mojom.gni, # NOTE: We would like to avoid scrambling message IDs where it doesn't add # value, so we limit the behavior to Mac and Windows desktop builds for now. enable_scrambled_message_ids = is_mac || is_win || (is_linux && !is_chromeos) || enable_nacl || is_nacl || is_nacl_nonsfi It says scrambling is enabled only on Mac and Windows, but apparently it's enabled on all platforms where nacl is enabled (incl. chromeos). One obvious fix is setting enable_scrambled_message_ids to false when is_chromeos is true.