Sometimes during ChromeOS booting into OOBE I get a message like:
ERROR:CONSOLE(1)] "Uncaught ReferenceError: login is not defined", source: (1)
This looks like a race. We need to figure out what is the source of this message.
I tried naive method of displaying all CallJS calls (see patch attached), but this seems to affect the timing and error disappeared.
Probably we should modify WebUI::GetJavascriptCall() to produce JS code that catches exceptions and displays a more friendly error message.
You may find this command-line useful to debug the issue:
time ninja -C out/Release/ -j3000 chrome chrome_sandbox && (UDD=$HOME/cros-test-user-data-dir-tmp ; rm -rf $HOME/cros-test-user-data-dir-tmp ; mkdir -p $HOME/cros-test-user-data-dir-tmp ; ./out/Release/chrome --login-manager --login-profile=user --user-data-dir=$UDD --disable-setuid-sandbox --no-sandbox --remote-debugging-port=9999 )
|
Deleted:
debug-calljs.patch
3.2 KB
|
Comment 1 by bugdroid1@chromium.org
, Mar 2 2017