Hint BrowserTaskEnvironment in task API failures

Print developer-friendly DCHECK failure messages in case the program
crashes due to misuse of Task APIs - e.g., trying to post a task to the
UI thread in a unit test without creating a BrowserTaskEnvironment.

This targets these two (mis)usage scenarios:
(1) calling content::GetUIThreadTaskRunner()/GetIOThreadTaskRunner()
    without having a BrowserTaskEnvironment;
(2) calling base::PostTask() with |content::BrowserThread::UI|/|::IO|
    without having a BrowserTaskEnvironment.

Before this change, these scenarios were triggering obscure crashes that
are hard to decipher for developers, namely:
* "[FATAL:browser_task_executor.cc(293)] Check failed:
  g_browser_task_executor." for scenario #1;
* "[FATAL:task_executor.cc(70)] Check failed: executor." for scenario #2.

In order to improve this, the following changes were made:

* A DCHECK message was added into
  base::GetRegisteredTaskExecutorForTraits() - the previous
  message-less DCHECK was preventing the helpful message in
  base::GetTaskExecutorForTraits()'s DCHECK from being reached.
  This helps in the scenario #2 from above.

* A DCHECK message was added into BrowserTaskExecutor::Get() that is
  analogous to the DCHECK message from base::GetTaskExecutorForTraits(),
  and code throughout the file was changed to use this Get() function
  instead of DCHECK'ing the same without any message.
  This helps in the scenario #1 from above.

* A Death unit test was added that verifies that scenarios #1 and #2
  trigger DCHECK failures that contain the "BrowserTaskEnvironment"
  substring, which would prevent from regressing in this debug logging
  again.

Bug: none
Change-Id: I959c4971537d2096321e573d148974f347a58f5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368600
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#804238}
3 files changed
tree: a0d00f4aea713cb959821079e9a9e3f13972c4d2
  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. cloud_print/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  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. .vpython
  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.

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.