This is an overview of the Net column in MemoryInfra.
To get an overview of total network stack memory usage, select the Browser process' net category and look at effective_size or size column.
The numbers are reported by the network stack’s MemoryDumpProvider, which is implemented by URLRequestContext class. URLRequestContext calls into major network stack objects (such as HttpNetworkSession, SSLClientSessionCache, HttpCache) to aggregate memory usage numbers. The total number reported in “net” is a lower bound of the memory used by the network stack. It is not intended to be an accurate measurement. Please use heap profiler instead to see all allocations.
This is a top-level network stack object used to create url requests. There are several URLRequestContexts in Chrome. See Anatomy of the Network Stack for what these URLRequestContexts are created for. The number of URLRequestContexts increases with the number of profiles.
For a “url_request_context” row, the “object_count” column indicates the number of live URLRequests created by that context.
This cache can be a disk cache (backed by either block file or simple cache backend) or an in-memory cache. An incognito profile, for example, has an in-memory HttpCache. You can tell this by whether mem_backend_size column is present for that particular URLRequestContext.
This network stack object owns socket pools, the HTTP/2 and QUIC session pools. There is usually a 1:1 correspondence from a URLRequestContext to an HttpNetworkSession, but there are exceptions. For example, the “main” URLRequestContext shares the same HttpNetworkSession with “main_media” URLRequestContext and “main_isolated_media” URLRequestContext.
This object is an entry to establish HTTP/1.1, HTTP/2 and QUIC connections.
This object owns HTTP/2 sessions.
This object owns QUIC sessions and streams.
This is a global singleton that caches SSL session objects which retain references to refcounted SSL Certificates.