Adds CHECKs in pursuit of message leaks

It appears that we may in some cases be leaking message objects.
Stacks from the wild indicate that these are often (if not always)
legacy IPC messages, which means there's a good chance it's a leak
either in the outgoing EDK channel backlog queue or in the IPC
Channel's internal outgoing message queue.

Bug: 813045
Change-Id: Id1663e36353c0f4325fbc53c829ded8d951a620c
Reviewed-on: https://chromium-review.googlesource.com/926565
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538488}

CrOS-Libchrome-Original-Commit: 37ddd815d13ecfeffe1e365f8a167601493f81a3
1 file changed
tree: 49f270c1d761f51cea3104e477528979804f9b54
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/