10,000 GDI Objects Ought to be. . .

. . . enough for anybody.

I keep my computer on 24/7 and run Outlook 24/7.  The only reason I’ve ever had to reboot is because my Outlook gets to a point where it won’t paint the screen correctly.

I had finally had enough today when I searched google and found the following article:
Ryan’s Look at Outlook Programmability : Outlook 2007 GDI Leak Hotfix

which pointed me to the hotfix here:
http://support.microsoft.com/kb/932406

According to Ryan, the problem has something to do with the interaction of my sidebar gadget that shows me the upcoming scheduled items and the fact that Vista only allows 10,0000 gdi objects per process.

There is a GDI leak in comctl32.dll that this hotfix fixes.

Related Post

  • DotNetNuke – Missing Content in ModulesDotNetNuke – Missing Content in Modules A couple of days ago, a client of mine called and said he'd been working on his DotNetNuke site moving things around when suddenly he was unable to see his module content any more. Since I'm his D...
  • Upgrading Vista 32 bit to Windows 7 64bitUpgrading Vista 32 bit to Windows 7 64bit Since I own an MSDN subscription, I was able to get my hands on a copy of Windows 7 last Thursday. I didn’t actually install it until this past Sunday because Sunday is the only day I don’t need...
  • UnauthorizedAccessException writing to HKLMUnauthorizedAccessException writing to HKLM Q. I'm trying to write to HKLM on a Vista computer using the following code:Dim k As Microsoft.Win32.RegistryKey k = Microsoft.Win32.Registry.LocalMachine.OpenSubKey("software", True) k = k.Creat...
  • Compiler Error Message: CS0016Compiler Error Message: CS0016 Last Thursday I was working with a client trying to get some code I had written running under his copy of IIS on Windows Vista. The full text of the message indicates that the .NET runtime was una...
  • DotNetNuke – FileUploadControl Danger!DotNetNuke – FileUploadControl Danger! A couple of days ago I was working with a client who was having trouble using the File Upload Control from within a DotNetNuke module. The problem we were seeing was that although all the code ...