Today the browser process registers to the memory-infra service in a special way [1].
It leverages the knowledge that the browser process is the same that hosts the memory-infra service, and bypasses the Mojo IPCs.
This causes the code in coordinator_impl.cc to behave in weird ways, because the messages received from the browser have no identity (see Issue 732927 ).
There doesn't seem to be any strong need of this (seems a premature optimization) and as such I'm going to ditch it soon to make everything easier to reason about.
[1] https://cs.chromium.org/chromium/src/services/resource_coordinator/memory_instrumentation/coordinator_impl.cc?rcl=9b2b6a840fc7c88f5c46b5a32d8d844d778f35e4&l=80
Comment 1 by bugdroid1@chromium.org
, Jun 22 2017