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

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task

issue 709008

Sign in to add a comment

Issue 708752: Implement Memory Pressure API

Reported by, Apr 5 2017 Project Member

Issue description

Feature description:
API to to expose the memory pressure signal received by the system to web applications. 

Eng owners:,

Design doc:


Comment 1 by, Apr 6 2017


Comment 2 by, Apr 17 2017

Blocking: 709008

Comment 3 by, Apr 18 2017

Reminder that if this has privacy/security/etc impacts it should also have a corresponding type=launch issue. For more details see

Comment 4 by, Jun 5 2017

Status: Available (was: Assigned)
We've decided to punt on this based on initial work & prototyping.
(google corp doc)

Comment 5 by, Sep 12 2017

Labels: migrated-launch-owp Type-Task
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here:

For any questions, please contact owencm, sshruthi, larforge

Comment 6 by, Sep 18 2017

Components: Privacy

Comment 7 by, Jan 4 2018

Shubhie, should we close this?

Comment 8 by, Apr 30 2018

Ping, is there still plans to implement this?

Comment 9 by, Apr 30 2018

Status: WontFix (was: Available)
Marking WontFix as per #4.

Sign in to add a comment