New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 693121 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
█ xunji...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Ensure network pings don't leave memory footprint

Project Member Reported by mariakho...@chromium.org, Feb 16 2017 
When the connection is off, Chrome creates network requests to random urls, e.g. http://dkfjskldfjlsdj/ to check for connectivity. Ensure that once done, there's no memory footprint left over.

Comment 1 Deleted

Comment 2 by mariakho...@chromium.org, Feb 21 2017

Labels: -Hotlist-EM

Comment 3 by mariakho...@chromium.org, Feb 22 2017

Labels: EM

Comment 4 by mariakho...@chromium.org, Feb 24 2017

Labels: -EM LowMemory

Comment 5 by ssid@chromium.org, Apr 29 2017

Cc: xunji...@chromium.org
xunjieli:
Caching semantics is specified by RFC and we need to be specs compliant regarding cache directives.

Reading more about RFC, there seems to be restrictions only on when the data can be stored in cache. I couldn't find any specification that says anything MUST be cached. Can you please expand a bit more on the specification you are talking about?

It'd be good to discard these connections / caches.

Comment 6 by xunji...@chromium.org, May 1 2017 

The random urls are from chrome/browser/intranet_redirect_detector.h. I don't think there're any HTTP caching semantics involved or real connections.
You can confirm it by getting a NetLog. Instructions are at https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details.

Comment 7 by mariakho...@chromium.org, Jul 17 2017

Status: WontFix (was: Available)
►

Sign in to add a comment