Fix MDnsClientImpl timer usage
Previously, cleanup timer (schedules cache cleanups for soonest TTL) would keep running after MDnsClientImpl::Core destruction but it used unretained references to the destroyed Core. Now it's always stopped on Core destruction. Also cleaned up MDnsClientImpl to ensure time is destroyed after Core to ensure the new Stop() call is always safe. Reordered fields and added a StopListening() call in the destructor. Bug: 958307 Change-Id: I6d3063e7f6a6ad49991ae41cbcab4739d81c5da8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1593841 Auto-Submit: Eric Orth <ericorth@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Reviewed-by:Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#656403}
Showing
Please register or sign in to comment