New implementation of font precache on Windows.

chrome/common/chrome_utility_messages.h

Index: chrome/common/chrome_utility_messages.h
diff --git a/chrome/common/chrome_utility_messages.h b/chrome/common/chrome_utility_messages.h
index c99365341c17b36163d82ce86b14bc21f53efb64..63694466173227e66386206a27296897e59e00f7 100644
--- a/chrome/common/chrome_utility_messages.h
+++ b/chrome/common/chrome_utility_messages.h
@@ -146,8 +146,13 @@ IPC_MESSAGE_CONTROL0(ChromeUtilityHostMsg_RenderPDFPagesToMetafile_Failed)
 #if defined(OS_WIN)
 // Request that the given font be loaded by the host so it's cached by the
 // OS. Please see ChildProcessHost::PreCacheFont for details.
-IPC_SYNC_MESSAGE_CONTROL1_0(ChromeUtilityHostMsg_PreCacheFont,
-                            LOGFONT /* font data */)
+IPC_SYNC_MESSAGE_CONTROL2_0(ChromeUtilityHostMsg_PreCacheFont,
+                            LOGFONT /* font data */,
+                            int /*pid*/)

[nsylvain, 2011/09/13 19:32:18]

should you really trust the renderer with the pid? A malicious renderer could
potentially screw your cache.  I'm pretty sure there is a way to get the
renderer pid within the message handler.

[arthurhsu, 2011/09/13 20:58:32]

This one is a service utility process host, which is used internally by
printing.  The other one used by renderer process is changed.

+
+// Release the cached font
+IPC_MESSAGE_CONTROL1(ChromeUtilityHostMsg_ReleaseCachedFont,
+                     int /*pid*/)
 #endif  // defined(OS_WIN)
 
 // Reply when the utility process successfully parsed a JSON string.