Shulou(Shulou.com)05/31 Report--

Today, I would like to talk to you about how to carry out in-depth analysis of Desktop heap, many people may not know much about it. In order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

In addition to using processes to manage resources, Windows uses Session and desktop to manage resources. For example, only processes in the same Session can share clipboard data, and Windows Message can only be passed between processes belonging to the same desktop. Desktop heap, on the other hand, is managed by the operating system, created for different session and shared by all desktop within the same session. When creating a process and creating a GUI, it consumes desktop heap. When the Desktop Heap is used up, all kinds of inexplicable problems in the system will occur.

For example, if you can't create a new process or pop up a menu, the API call will go wrong inexplicably.

Desktop heap often runs out because too many processes are running at the same time, or too many GUI object are created. When you suspect that it is a Desktop heap-related problem, you can first use the method of the following article to check whether Desktop heap is used up:

First, go to Desktop Heap Monitor Version 8.1 to download the installer.

During installation, the relevant files will be automatically unzipped to the c:\ kktools directory, but not automatically.

Then execute the following batch file directly, and you can automatically complete all the actions that should be done.

When you want to see the current Desktop Heap Size, you can directly click the batch file to complete all the steps, and the batch file will automatically uninstall the driver, which will not cause a burden on your computer. Modify 3072, 8192, 10240, 15360, 20480, etc.

The parameter MaxRequestThreads specifies the maximum number of threads that can be managed. By default, this number is nearly 16, and someone has changed this parameter to 80 (whether it is valid or not)

Microsoft claims to modify the second value of SharedSection, 3072, which can be changed to "4096" or "8192" to solve the problem of running a large number of programs running out of memory.

MS calls this value "desktop heap".

If it is confirmed that it is a desktop heap problem, you can refer to changing the registry to make adjustments.

Enter the registry through the regedit.exe command and find the registry parameters according to the following path:

HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Session Manager\ SubSystems\ Windows

Where Windows is a string parameter, and the default value is as follows (each part is separated by spaces):

% SystemRoot%\ system32\ csrss.exe ObjectDirectory=\ Windows SharedSection=1024,3072512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

Note: each system Desktop object has a heap corresponding to it, and the Desktop object uses heap (heap) to store menus, strings, forms, and so on. The system allocates desktop heap from the core cache (48m). A WINDOWS operating system can have multiple desktop heap.

Because under a non-interactive workstation, SCM creates a new desktop for each service process of a user account, a higher desktop heap value will reduce the number of user accounts that the system can serve. Desktop heap cannot be understood as a "stack for remote desktops".

After reading the above, do you have any further understanding of how to do in-depth Desktop heap parsing? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.