We build headless_shell and chromedriver to use with selenium for completely headless arm64 and x64 systems and with chromium 102.0.5005.115 we end up with large delays when doing selenium send_keys to an input field. In the chromedriver log we get hundreds of repeated instances of the following for multiple seconds before the keys are actually sent to headless_shell:
[04-14-2023 10:35:04.696344][SEVERE]: Check failed: keyboard_layout_engine_.
...
[04-14-2023 10:35:07.328840][SEVERE]: Check failed: keyboard_layout_engine_.
[04-14-2023 10:35:07.328882][DEBUG]: DevTools WebSocket Command: Input.dispatchKeyEvent (id=99) 532C548E20982B81C330D869307C5F7F {
"code": "KeyN",
"key": "n",
"modifiers": 0,
"text": "n",
"type": "rawKeyDown",
"unmodifiedText": "n",
"windowsVirtualKeyCode": 78
}
We build chromedriver with the following GN args:
target_os=\"linux\"
target_cpu=\"${ARCH}\"
use_ozone = true
ozone_auto_platforms = false
ozone_platform = \"headless\"
ozone_platform_headless = true
headless_use_embedded_resources = true
headless_fontconfig_utils = true
use_bundled_fontconfig = true
icu_use_data_file = false
v8_use_external_startup_data = false
enable_nacl = false
enable_print_preview = false
enable_remoting = false
use_alsa = false
use_cups = false
use_dbus = false
use_gio = false
use_kerberos = false
use_libpci = false
use_pulseaudio = false
use_udev = false
rtc_use_pipewire = false
v8_enable_lazy_source_positions = false
use_glib = false
use_gtk = false
use_pangocairo = false
use_x11 = false
symbol_level = 0
is_component_build = false
enable_nacl = false
use_kerberos = false
is_debug = false
We are using the same GN args that we have used for more than year to build headless_shell/chromdriver 88.0.4324.182 with no issue. Any ideas on what could be wrong with the chromedriver build to cause the above send_keys issue?