UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3570.0 Safari/537.36

Steps to reproduce the problem:
1. Enable BookmarkBarViewTest24.ContextMenusKeyboardEscape
2. Run interactive_ui_tests with filter & repeat on linux-xenial-rel trybot 

What is the expected behavior?
All iterations of the test succeeed.

What went wrong?
Some of the test iterations may (or may not) cause the following error

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x60000d
  Serial number of failed request:  473
  Current serial number in output stream:  474

Did this work before? N/A 

Chrome version: 71.0.3570.0  Channel: n/a
OS Version: 16.04
Flash Version: 

Many attempts to reproduce and track this down were made on the actual failing machine which can reproduce the issue. There is no local debugger, symbols or stack dump available.
A local VM using Ubuntu 16.04 with the latest patches was also tried, yet no failure was ever encountered with and without xvfb.
All other Linux versions used for building/testing also succeed.
 

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3570.0 Safari/537.36

Steps to reproduce the problem:
1. Enable BookmarkBarViewTest24.ContextMenusKeyboardEscape
2. Run interactive_ui_tests with filter & repeat on linux-xenial-rel trybot 

What is the expected behavior?
All iterations of the test succeed.

What went wrong?
Some of the test iterations may (or may not) cause the following error

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x60000d
  Serial number of failed request:  473
  Current serial number in output stream:  474

Did this work before? N/A 

Chrome version: 71.0.3570.0  Channel: n/a
OS Version: 16.04
Flash Version: 

Many attempts to reproduce and track this down were made on the actual failing machine which can reproduce the issue. There is no local debugger, symbols or stack dump available.
A local VM using Ubuntu 16.04 with the latest patches was also tried, yet no failure was ever encountered with and without xvfb.
All other Linux versions used for building/testing also succeed.