From 5ac2016d3695d469206aad51f04c211a84f1d32f Mon Sep 17 00:00:00 2001 From: "gspencer@chromium.org" Date: Wed, 24 Nov 2010 23:33:11 +0000 Subject: This is another try to commit OOM priority management. This changes nothing, except that I now initialize memory_used in oom_priority_manager.cc to placate the incorrect gcc warning about it being used when uninitialized. The original review is here: http://codereview.chromium.org/4498001/ BUG=none TEST=Passed chromeos try-bot, built both debug and release locally. Review URL: http://codereview.chromium.org/5328003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67342 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/zygote_host_linux.h | 3 +++ 1 file changed, 3 insertions(+) (limited to 'chrome/browser/zygote_host_linux.h') diff --git a/chrome/browser/zygote_host_linux.h b/chrome/browser/zygote_host_linux.h index dd00336..ffb7964 100644 --- a/chrome/browser/zygote_host_linux.h +++ b/chrome/browser/zygote_host_linux.h @@ -67,6 +67,9 @@ class ZygoteHost { return 0; } + // Adjust the OOM score of the given renderer's PID. + void AdjustRendererOOMScore(base::ProcessHandle process_handle, int score); + private: friend struct DefaultSingletonTraits; ZygoteHost(); -- cgit v1.1