We have an internal report that the utility process, which is spawned by DeviceDescriptionService as part of in-browser DIAL discovery, lingers and appears to be idle after parsing activity has completed. It isn't clear why this occurs sometimes, though, since the code does tear down the UtilityProcessMojoClient when there are no more parsing requests.
With https://chromium-review.googlesource.com/c/chromium/src/+/770920 we are changing the DIAL discovery code to use a generic XML parser process exposed by service_manager. Since the lifetime of the process would be maintained by service_manager with this change, it is possible that the problem will be fixed. The purpose of this bug is to verify that the process is torn down properly when idle, or to track down the underlying cause if it still persists.
Comment 1 by bugdroid1@chromium.org
, Nov 30 2017