As an aside, favicons are handled in the renderer, sandboxed. The renderer decodes them and reencodes them as PNG to ensure that they're safe before handing them off to the browser process. Trace the ViewMsg_DownloadFavIcon, ViewHostMsg_UpdateFavIconURL, and ViewHostMsg_DidDownloadFavIcon messages for more detail.
Avi On Wed, Jul 29, 2009 at 12:00 PM, Avi Drissman <[email protected]> wrote: > On Wed, Jul 29, 2009 at 11:52 AM, Mike Pinkerton > <[email protected]>wrote: > >> Don't we farm out a separate process for favicon decoding? And for >> theme image decoding as well? > > > There are two things done by the utility process. Unpacking of themes (not > just images but the unzipping of the packages, parsing of the JSON, and > unpacking the images) and unpacking of "web resources". That's > WebResourceService, which seems right now to be used for the external "tips > list". > > Favicons do not appear to be handled by the utility process. > > Avi > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
