Landing page for all things memory-related in Chromium.
Look at the UMAs Memory.{Total,Renderer,Browser,Gpu,Extension}.PrivateMemoryFootprint.
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://chromium.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. |
Follow these instructions to file a high quality bug.
See this page for further instructions.
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. |
There are roughly three types of memory work within Chrome:
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 |
Heap Profiling | alph, erikchen, ssid, etienneb |
Net Stack | mmenke, rsleevi, xunjieli |
Renderer Process | haraken, tasak, hajimehoshi, keishi, hiroshige |
V8 | hpayer, ulan, verwaest, mlippautz |