Last week I was working and suddenly PC started acting strange. It had lag and the UI of Adobe Reader X was almost totally disposed.
The first thing that I did was checking the number of GDI objects from Adobe Reader X. If the UI is having problems drawing itself and the program is not responding as it should be, that could be a good place to start your search.
Checking the GDI objects in Windows is very simple:
- Press Ctrl+Shift+Esc to open the Task Manager
- Select the [Processes] tab
- Add the GDI Objects column by clicking [View] > [Select Columns…] and check [GDI Objects]
- Now find your Adobe Reader X process in the list and check how much GDI Objects it has.
The limit of GDI Objects per process is 10000 in Windows, and that is what I actually saw.
The problem occurs when you open a PDF file and press Ctrl+F and search for some text. You will not notice the leak if you don’t use (= scrolling and searching) the PDF file for a while.
By scrolling the document, everything works fine but if you search the document it will leak GDI handles and if you scroll after you triggered the leak, every scroll will increment the leaked handles.
I just binged if this was a new bug but it seems that this bug was already reported in February 2011 on the Adobe forums.
Shame on you Adobe!
FYI: tested on Windows 7 (x64) and again another reason to start using the free Foxit Reader.