Link ServiceWorkerVersion in-flight requests to event queue idle timeout

ServiceWorkerVersion in-flight requests can block idle timeout request
from event queue. However they couldn't extend the idle timer. As a
result extension service worker events, which leverage in-flight
requests, cannot guarantee 30 seconds idle time.

In this CL we reuse the idle timeout callback logics in
ServiceWorkerEventQueue. That is, 1) cancel the idle timeout when
starting an event; 2) check event queue when finished an event, schedule
the idle timeout if the event queue is empty.

Before checking event queue we also check if there is any in-flight
requests. This makes sure idle timeout is scheduled only when in-flight
request queue is empty too.

ServiceWorkerEventQueue logic remain unchanged. There might be a case
that idle timeout is scheduled when there are ongoing in-flight
requests.
Which is okay because ongoing in-flight requests will block termination
request. And by the time in-flight request finishes the idle timeout may
be rescheduled.

R=lazyboy@chromium.org, rdevlin.cronin@chromium.org

Change-Id: I901727d70d1130d0c55fe38f38e507fdc91c4304
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4022172
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Richard Zhang <richardzh@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081592}
8 files changed
tree: f544abb43da8d2bd212a454fe20cd8fcd5a85782
  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.