Across all. The most of any one process (I think it was the browser process,
but not 100% sure, could be a long-lived renderer) was something like 300
total handles, 150 of which were font.
On Thu, Feb 5, 2009 at 10:11 PM, Brett Wilson <bre...@chromium.org> wrote:
> On Thu, Feb 5, 2009 at 9:29 PM, Ian Fette <i...@chromium.org> wrote:
> > Once again, my laptop is refusing to stand by and Windows is throwing up
> > warning dialogs about "Insufficient system resources exist to complete
> the
> > API." Currently Chrome is sucking down a healthy 1043 gdi handles
> according
> > to gdiview, 647 of which appear to be font handles...
> > What is a reasonable number to expect Chrome to be using? Is 647 font
> > handles indicative of a leak? For reference, I have 23 chrome processes
> > running, and a healthy (or unhealthy?) number of tabs.
>
> Is 647 font handles across all chrome processes? If that's across all
> 23 processes, it's not a problem. 1000 GDI objects is a lot and more
> than normal, but it depends on what sites you've been visiting because
> of the font cache. For reference, I've got <200 GDI objects per chrome
> process, and I have two visual studio instances open and each is using
> 750 GDI objects.
>
> Brett
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
