Cleanup XR Session Shutdown paths

Attempgs to cleanup/reorganize some of the VR Shutdown paths and make
things a little bit clearer. Specifically:

1) Removes on_presentation_ended from the CompositorBase::RequestSession
interface. The only remaining caller was openxr, which simply passed a
base::DoNothing. It's possible that future refactors to OpenXr::
ShutdownSession will want a callback at the end; but this is better
handled by passing such a callback to ExitPresent directly.

2) Removes VrDeviceBase::ShutdownSession. This forces children to
implement this method directly, rather than relying on the default
backwards compatible, but not necessarily precise behavior.

3) Implements ShutdownSession for VrOrientationDevice, this is still
just an immediate return of the session; but there's nothing really
blocking on the device side if an inline session is still outstanding
like there is for an immersive session.

4) Implements ShutdownSession for OpenXRDevice. It still returns a bit
too early; but it at least now actually kicks off a shutdown rather than
waiting for the PresentationProvider pipe to be disconnected; which is
the current way that an OpenXRDevice gets notified of a shutdown. This
introduces a little bit of refactoring to share code with the existing
shutdown path.

5) Adds an "already exited" check to OpenXrRenderLoop to avoid multiple
calls. All of the operations should be resilient to multiple calls, but
it saves a little cognitive overhead for developers.

Future work in this area should address not calling the ShutdownSession
callback in OpenXRDevice until the Session is fully shutdown. It should
be possible to further simplify the session shutdown flow by removing

all the way in to the device; which could then mimic the "OnExitPresent"
call by disconnecting the XRSessionClient. This has the added benefit of
remvoing an unneeded hope for the VisibilityStateChanged method.

XrRuntimeEventListener: :OnExitPresent and passing the XRSessionClient
Change-Id: I7df95eda6d30668187cca1d5827086282bd4eda5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4054022
Reviewed-by: Piotr Bialecki <bialpio@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1076371}
11 files changed
tree: 4959fad8627c2ec4e54cd54b825328fda90487b4
  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_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.