Pushing the Limits of Windows: Handles 7faK9s2c8@1M7s2y4Q4x3@1q4Q4x3V1k6Q4x3V1k6T1L8r3!0Y4M7#2)9J5k6i4c8W2j5$3S2F1k6i4c8Q4x3X3g2E0K9h3y4J5L8%4y4G2k6Y4c8Q4x3X3g2U0L8$3#2Q4x3V1k6E0j5i4u0C8M7Y4g2K6M7$3W2F1L8%4k6A6j5$3S2Q4x3V1j5J5x3o6l9&6i4K6u0r3x3o6W2Q4x3V1j5J5z5g2)9J5c8Y4m8#2M7$3S2A6L8X3N6Q4x3X3c8@1K9r3g2Q4x3X3c8D9K9h3#2A6N6s2y4Q4x3X3c8G2k6W2)9J5k6s2N6A6L8X3c8G2N6%4y4Q4x3X3c8Z5j5h3&6V1L8r3g2K6i4K6u0r3
GDI Objectsare resources that are managed by GDI32.DLL on behalf of an application. Some of the most common types of GDI objects are Device Contexts (DCs), Bitmaps, Brushes, Fonts, Metafiles, Pens, and Regions. GDI Objects are stored in Kernel Memory (specifically the Paged Pool or Session Pool portions of kernel memory – more on this later).
GDI Handlesare unique identifiers of a GDI Object. Each GDI Object can have only one handle. Each GDI Handle is process-specific (cannot be used by other processes).