zookeeperX" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
Subject: **UPDATE** IE7 Right click/New tabs/Menus Issues **UPDATE**
Date: Tue, 20 Nov 2007 02:25:01 -0800
Notice that I was only pointing out that GDI >9000 can cause the same
symptoms that you are reporting. It is one example of a more general
issue of resource shortage (which may be due to inefficient programming
or bugs (e.g., in the form of leaks) or just a lack of tuning needed to adapt
for a particular user's extraordinary needs.).
So, are any of the other numbers changing dramatically?
Try taking note of the numbers for whatever set of tabs you have
at that time. For this I think there are better tools than TM but
I suppose you could try using Alt-PrintScrn and saving however
many rightscrolls it would take to capture them all into a Clip Book.
(Assuming Vista still has clipbrd.exe to Run... but hopefully something
even better?) In fact for this case you could ignore cumulative statistics
such as page faults and I/O counts which could reduce the number of
screens you would have to capture.
Hmm... I just checked in Process Explorer's Help. It has a feature
which might be simpler than the proposed ClipBook idea. Supposedly
once you have selected your iexplore.exe process it could be just as
easy as pressing Ctrl-s... then finding the saved file and opening it
with Notepad. (Seems to work.)
When you choose File|Save Process Explorer saves the contents of
the Process and lower pane, if it is showing, as a tab-delimited text file.
Another option which would be more work to set up but which would ultimately
be more useful for comparing the statistics from multiple instances would be
to use PerfMon to keep a log of the equivalent statistics we are interested in.
And again, if there are any better tools now in Vista someone else is going
to have to point them out to you.
So, however you do it (even manually using Notepad <w>) get some numbers
and then close your IE window, using the option which says that you want to
reopen the same set of tabs the next time you start it again. Then compare
the set of statistics for the new instance of the browser with the saved set.
If you had a leak in the first instance it would probably be apparent as a much
lower statistic in the second instance (e.g. not necessarily GDI Objects).
BTW from the above search it looks as if you and WayneF could start commiserating:
Subject: Re: IE uses too many GDI Objects (Slows PC)
Date: Mon, 22 Oct 2007 09:35:28 +0200
Interesting that you can go to 9,900 GDI objects yet if i get to 6,000
.... the computer is basically useless ....
FWIW I think that in spite of the thread's Subject that GDI Objects
may not be the issue.
Hmm... that poster was using XP but found an article whic