Issue metadata
Sign in to add a comment
|
NetworkQualityObserver leaks / allocates lot of mojo handles |
||||||||||||||||||||||||
Issue descriptionFound quite a few reports from users with large memory usage from NetworkQualityObserverImpl tasks on Android and desktop. The large ones were 40MB on Android and crash/7347ce5121605438#6 and 160MB on Windows crash/27fe06b49dd8bff538%27#6 The Android browser and renderer were alive for 3 days before the trace was taken. I guess a lot of times the network was changed and the observer sends mojo messages. I am not sure if this is a leak or we just use so many handles
,
Feb 3 2018
,
Feb 3 2018
Assigning to owner of nqe for now.
,
Feb 3 2018
This seems very similar to Issue 798025 .
,
Feb 3 2018
,
Feb 6 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3e7284bb4e047557f5fc2b39164a4c9495be2bd5 commit 3e7284bb4e047557f5fc2b39164a4c9495be2bd5 Author: Ken Rockot <rockot@chromium.org> Date: Tue Feb 06 16:11:16 2018 Ensure that queued IPC messages can't leak Assuming based on a small amount of evidence that there may be a bug causing some ChannelAssociatedGroupController instances to leak, this CL ensures that in such cases, the object's outgoing message queue will not also leak. Bug: 808725 Change-Id: I256dd264b811f9ccb8e8e3ee86f2b58f916f1560 Reviewed-on: https://chromium-review.googlesource.com/902813 Reviewed-by: Yuzhu Shen <yzshen@chromium.org> Commit-Queue: Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#534693} [modify] https://crrev.com/3e7284bb4e047557f5fc2b39164a4c9495be2bd5/ipc/ipc_mojo_bootstrap.cc |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ssid@chromium.org
, Feb 3 2018