Skip to content

Latest commit

 

History

History
88 lines (62 loc) · 4.62 KB

README.md

File metadata and controls

88 lines (62 loc) · 4.62 KB

Memory

Landing page for all things memory-related in Chromium.

The goal is to keep an up-to-date set of links and references that will help people understand what is actively happening in the memory space. Please keep this landing page short and action oriented.

That being said, please also send CL with update and changes. This should reflect current active status, and it's easier to do that if everyone helps maintain it. :)

How is chrome's memory usage doing in the world?

Look at the UMAs Memory.{Total,Renderer,Browser,Gpu,Extension}.PrivateMemoryFootprint.

These metrics are known to lack sufficient context. e.g. How many renderers are open? What site is a renderer hosting? How long has the browser been running?

Some of these graphs are now available at go/mem-ukm.

How do developers communicate?

Note, these channels are for developer coordination and NOT user support. If you are a Chromium user experiencing a memory related problem, file a bug instead.

name description
[email protected] Discussion group for all things memory related. Post docs, discuss bugs, etc., here.
[email protected] Google internal version of the above. Use sparingly.
https://chromiumdev.slack.com/messages/memory/ Slack channel for real-time discussion with memory devs. Lots of C++ sadness too.
crbug Performance=Memory label Bucket with auto-filed and user-filed bugs.
crbug Stability=Memory label Tracks mostly OOM crashes.

I have memory problem, what do I do?

Follow these instructions to file a high quality bug.

I'm a developer trying to investigate a memory issues, what do I do?

See this page for further instructions.

I'm a developer looking for more information. How do I get started?

Great! First, sign up for the mailing lists above and check out the slack channel.

Second, familiarize yourself with the following:

Topic Description
Key Concepts in Chrome Memory Primer for memory terminology in Chrome.
memory-infra The primary tool used for inspecting allocations.

What are people actively working on?

Project Description
Purge+Throttle/Suspend Centralized policy and coordination of all memory components in Chrome
Memory-Infra Tooling and infrastructure for Memory
System health benchmarks Automated tests based on telemetry
Out of Process Heap Profiling Collect heap dumps from the wild
Always on Document Leak Detector UMA-based sanity check that DOM objects are not leaking in the wild.
Real-world leak detector Runs blink leak detector on top-sites [web-page-replay] on waterfall.

Key knowledge areas and contacts

Knowledge Area Contact points
Chrome on Android lizeb, pasko, ssid
Browser Process ssid, erikchen, etienneb
GPU/cc ericrk
Memory metrics ssid, erikchen, primano, ajwong, wez
Native Heap Profiling primiano, ajwong
Net Stack mmenke, rsleevi, xunjieli
Renderer Process haraken, tasak, hajimehoshi, keishi, hiroshige
V8 hpayer, ulan, verwaest, mlippautz
Out of Process Heap Profiling erikchen, ajwong, brettw, etienneb

Other docs