| commit | 4caf4e46014437d362853a8b532b734ef2c41ca8 | [log] [tgz] |
|---|---|---|
| author | Etienne J. Membrives <etiennej@fuchsia.infra.roller.google.com> | Fri Jan 31 06:45:57 2025 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 31 06:48:12 2025 -0800 |
| tree | 6c37766e6910e2c10aef3d9302f3e8279a4d2008 | |
| parent | 75c4cd7c1cb3b31c6b7e1048858cd44624c8c520 [diff] |
[roll] Roll fuchsia [memory_monitor] Don't force-capture on IMMINENT_OOM Today, we force a memory capture when entering the IMMINENT_OOM pressure state. This has two issues: - When memory monitor is configured to not capture on memory pressure changes, it is still capturing on this particular memory pressure change, which is not the intention of the configuration flag. - When memory monitor is configured to capture on memory pressure changes, we capture twice in quick succession. This change removes the force-capture on IMMINENT_OOM, and instead does the regular capture on memory capture change, including when reaching IMMINENT_OOM, if configured for that. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1197175 Original-Revision: 0e2533a77d13aecac61ee0f2b78f68969619e507 GitOrigin-RevId: fe2491056dc5507f77870e73d072208262c24533 Change-Id: I27ca251c647b3f70067c3c2ae3c1d6b81e6c5dc2
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.