Filter command responses from detached CDP sessions

Sometimes, ChromeDriver can receive a command response for a command
sent to a session that has been detached. The repro steps are something
like this:

1. DevToolsClientImpl for the root session 'A' calls SendCommand and
   polls for a response.
2. An event is received for a nested DevToolsClientImpl session 'B'.
3. DevToolsClientImpl 'B' sends a nested command as part of the event
   handler and polls for a response.
4. Session 'B' detaches while DevToolsClientImpl 'B' is waiting for a
   response, so this DevToolsClientImpl stops polling and detaches.
5. Later, the browser processes the command from session 'B'. The
   CDP session is already gone, so the browser responds with an error
   message containing no "sessionId" property.
6. DevToolsClientImpl 'A' is still polling since step 1 and receives
   the error message from step 5.
7. Since the error message has no sessionId, it is handled by the
   root DevToolsClientImpl 'A'.
8. The message has an "id" that is not in DevToolsClientImpl 'A's map
   so DevToolsClientImpl::ProcessCommandResponse returns an error.
   The polling stops and the SendCommand call for step 1 fails.

The fix is to detect this condition in ProcessCommandReponse. If the
CDP reponse is a "session not found" error and the "id" is
unrecognized, then simply ignore this message and continue pumping
other messages.

The fix has been verified with the repro in the attached bug.

(cherry picked from commit f1795ca9f858cf76d98d01a4f4314b5ecb778be1)

Bug: chromium:1340174, chromedriver:4121
Change-Id: I6238de74dacb7fd2bc5e115ca5b6625232ce9ac3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3658212
Commit-Queue: Brandon Walderman <brwalder@microsoft.com>
Reviewed-by: Vladimir Nechaev <nechaev@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1006507}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3751214
Commit-Queue: Vladimir Nechaev <nechaev@chromium.org>
Auto-Submit: Vladimir Nechaev <nechaev@chromium.org>
Reviewed-by: Alex Rudenko <alexrudenko@chromium.org>
Cr-Commit-Position: refs/branch-heads/5060@{#1169}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
2 files changed
tree: b61263e18d1a1b552b30fcb6bbea855e58633d6a
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.