Chrome Version: Google Chrome 71.0.3573.0 (Official Build) canary (64-bit)
Revision 540477605ecd461a31985e4fcd67e8786e895802-refs/branch-heads/3573@{#1}
OS: MacOS 10.13.6
What steps will reproduce the problem?
(1) put machine to sleep on wednesday
(2) wake on Monday
(3) see ports ugh
What is the expected result?
What happens instead?
Please use labels and text to provide additional information.
If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
Comment 1 by meh...@chromium.org
, Oct 8Components: Internals>Network>DNS
Labels: -Pri-3 Pri-2