Method and device for adjusting priority of application process memory release

Abstract

The embodiment of the invention provides a method and device for adjusting the priority of application process memory release, and relates to the technical field of embedded computer software. The priority of the application process memory release of a non-activity interface can be adjusted. The method includes the steps that a window of an application process in a display frame service of an operating system is monitored according to the name of the application process, and the application process is a non-activity interface application process; the priority of the application process is set according to the change state of the window so that memory release can be conducted in accordance with the priority of the application process. The method and device are used for adjusting the priority.

Description

technical field [0001] Embodiments of the present invention relate to the technical field of embedded computer software, in particular to a method and device for adjusting the priority of application process memory release. Background technique [0002] The hardware resources of embedded computer systems are relatively limited, especially the runtime memory (English abbreviation: RAM, English full name: Random-AccessMemory) is generally not too large, and embedded software generally optimizes memory usage to minimize memory usage and speed up The memory is released, but the system memory resources will still be tight when there are many programs running. The software of some embedded products will compress the memory in real time, and some will also enable the disk cache. However, considering that memory compression takes up processor resources, the running speed of the software will slow down, and the frequent reading and writing of the disk cache will affect the life of th...

AI Technical Summary

Problems solved by technology

However, if the resident attribute is not added, the non-Activity interface application will have the risk of being killed when the foreground is running. After adding it, it will affect the operating efficiency and memory resources of the system. The application of this resident attribute will always occupy memory. Even if the application is in an inactive state and is not displayed in the foreground, the memory cannot be released by the operating system, which reduces the total available memory of the system and increases the probability of system memory shortage. It is not suitable for embedded systems with low memory

To sum up, there is no technology that can adjust the priority of the application process of the non-Activity interface, so as to prevent the application of the non-Activity interface from being killed by the memory releaser due to memory shortage when it is displayed in the foreground, or The waste of system memory resources caused by setting the priority of the application process of the non-Activity interface as a resident attribute

Images