![]() ![]() ![]() In most cases the limits on handles are far beyond what typical applications or a system ever use. There are two limits related to the number of handles a process can create: the maximum number of handles the system sets for a process and the amount of memory available to store the handles and the objects the application is referencing with its handles. Handles are data structures that represent open instances of basic operating system objects applications interact with, such as files, registry keys, synchronization primitives, and shared memory. This time I’m going to go inside the implementation of handles to find and explain their limits. ![]() Pushing the Limits of Windows: USER and GDI Objects – Part 2 Pushing the Limits of Windows: USER and GDI Objects – Part 1 Pushing the Limits of Windows: Processes and Threads Pushing the Limits of Windows: Paged and Nonpaged Pool Pushing the Limits of Windows: Virtual Memory Pushing the Limits of Windows: Physical Memory While they can stand on their own, they assume that you read them in order. ![]() Here’s the index of the entire Pushing the Limits series. Series where I explore the upper bound on the number and size of resources that Windows manages, such as physical memory, virtual memory, processes and threads. First published on TechNet on Sep 29, 2009 ![]()
0 Comments
Leave a Reply. |