diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-19 23:35:50 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-08-19 23:35:50 +0000 |
| commit | 2ccf45c50fad0f2c3c20d95eef6d0040b565b291 (patch) | |
| tree | 73eac41769a4678fcdb566e78d6e3bde7c10617c /chrome/browser/memory_purger.cc | |
| parent | da930e1b7adfb28f6895d95004c25984af627080 (diff) | |
| download | chromium_src-2ccf45c50fad0f2c3c20d95eef6d0040b565b291.zip chromium_src-2ccf45c50fad0f2c3c20d95eef6d0040b565b291.tar.gz chromium_src-2ccf45c50fad0f2c3c20d95eef6d0040b565b291.tar.bz2 | |
Prefix all IPC messages used by src\chrome with Chrome. For e.g ChromeViewMsg_, ChromeViewHostMsg, etc.
This makes it easier to identify which messages are specific to content and chrome.
This is a preparation CL for bug http://code.google.com/p/chromium/issues/detail?id=87335 which
requires IPC's to not span across content and chrome. When IPC's cross these boundaries they need
to be handled as API calls.
BUG=87335
Review URL: http://codereview.chromium.org/7631063
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@97536 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/memory_purger.cc')
| -rw-r--r-- | chrome/browser/memory_purger.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/chrome/browser/memory_purger.cc b/chrome/browser/memory_purger.cc index f728447..8f0546d 100644 --- a/chrome/browser/memory_purger.cc +++ b/chrome/browser/memory_purger.cc @@ -152,5 +152,5 @@ void MemoryPurger::PurgeRenderers() { // static void MemoryPurger::PurgeRendererForHost(RenderProcessHost* host) { // Direct the renderer to free everything it can. - host->Send(new ViewMsg_PurgeMemory()); + host->Send(new ChromeViewMsg_PurgeMemory()); } |