Repository navigation
Block Chrome's push channel to mtalk.google.com - #2574
Merged
Merged
Conversation
Every Chrome start opens a long-lived connection to mtalk.google.com on port 5228 (GCM/FCM push), even with --disable-background-networking. The WebPageReplay rules only map ports 80 and 443, so the connection went to the real internet during measurements and added background network work to every run. Mapping the host to ^NOTFOUND makes the lookup fail inside Chrome without sending any packets. Assisted-by: Claude Opus 5.5 noreply@anthropic.com Change-Id: Ic3b2a96d077a5290909dcaaf2a9ce4b150d7d49c
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every Chrome start opens a long-lived connection to mtalk.google.com on port 5228 (GCM/FCM push), even with --disable-background-networking. The WebPageReplay rules only map ports 80 and 443, so the connection went to the real internet during measurements and added background network work to every run.
Mapping the host to ^NOTFOUND makes the lookup fail inside Chrome without sending any packets.
Assisted-by: Claude Opus 5.5 noreply@anthropic.com
Change-Id: Ic3b2a96d077a5290909dcaaf2a9ce4b150d7d49c