CN111552616A - Memory monitoring method and device - Google Patents
Memory monitoring method and device Download PDFInfo
- Publication number
- CN111552616A CN111552616A CN202010365031.2A CN202010365031A CN111552616A CN 111552616 A CN111552616 A CN 111552616A CN 202010365031 A CN202010365031 A CN 202010365031A CN 111552616 A CN111552616 A CN 111552616A
- Authority
- CN
- China
- Prior art keywords
- application program
- memory
- phantomreference
- referencequeue
- garbage collection
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3037—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a memory, e.g. virtual memory, cache
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0253—Garbage collection, i.e. reclamation of unreferenced memory
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a memory monitoring method and device. The method is applied to terminal equipment of an android operating system, an application program is installed in the android operating system, and the method comprises the following steps: referencing Object objects in an application program in a PhantomReference mode in the application program, and associating ReferenceQueue objects for the PhantomReference; starting a monitoring thread for reading the ReferenceQueue object; if the referenceQueue Object is not empty, reading a PhantomReference Object stored in the referenceQueue Object, and determining that garbage collection behavior occurs in an application program where an Object referenced by the PhantomReference Object is located when the PhantomReference Object is successfully read; and judging whether the used memory amount of the application program with the garbage collection behavior exceeds a threshold value, and if so, determining that the application program with the garbage collection behavior enters a low memory state. By applying the method and the device, the occurrence of the low memory state can be monitored in the application program in time.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a memory monitoring method and apparatus.
Background
In a terminal device of an Android operating system (Android), Applications (APPs) of various functions may be installed. Each APP has an upper limit on memory usage. When the memory occupied by a certain APP exceeds the upper limit, an oom (out Of memory) crash occurs, which causes various exceptions such as APP crash and flash back.
Therefore, android software developers have the requirement of 'APP low memory monitoring', and hopefully, early warning callback can be obtained when the residual available memory of the APP is low, so that some occupied memories are released, the occupied memory of the APP cannot exceed the upper limit, and the APP can run more stably for a longer time.
As is well known, the Android operating system is an open source operating system developed by Google (Google) corporation. No low memory snoop and callback mechanism aiming at the APP level is designed in the android operating system. Therefore, even though android software developers have a demand for APP low memory snooping, APP low memory snooping cannot be achieved.
Disclosure of Invention
In view of this, the present application provides a memory snooping method and apparatus, and an electronic device. The method is used for solving the problem that the low memory of the APP cannot be determined in time.
Specifically, the method is realized through the following technical scheme:
in a first aspect, a memory monitoring method is provided, which is applied to a terminal device of an android operating system, where an application program is installed in the android operating system, and the method includes:
referencing Object objects in an application program in a PhantomReference mode in the application program, and associating ReferenceQueue objects for the PhantomReference;
starting a monitoring thread for reading the ReferenceQueue object;
if the referenceQueue Object is not empty, reading a PhantomReference Object stored in the referenceQueue Object, and determining that garbage collection behavior occurs in an application program where an Object referenced by the PhantomReference Object is located when the PhantomReference Object is successfully read;
and judging whether the used memory amount of the application program with the garbage collection behavior exceeds a threshold value, and if so, determining that the application program with the garbage collection behavior enters a low memory state.
Optionally, the method further includes:
and after the Object referenced by the PhantomReference Object is recycled by a garbage collector, adding the PhantomReference Object into a referenceQueue Object.
Optionally, the method further includes:
recovering memory resources occupied by the determined application program entering the low memory state; the recycled memory resource is a memory occupied by the running of unnecessary functions in the application program.
Optionally, the method further includes:
if the ReferenceQueue object is empty, blocking the monitoring thread; and the monitoring thread is awakened after being updated by the ReferenceQueue object.
Optionally, after determining that garbage collection is performed on the application program where the Object referenced by the PhantomReference Object is located, the method further includes:
and newly referencing the Object in the application program in a PhantomReference mode in the application program, and associating a referenceQueue Object for the PhantomReference.
In a second aspect, a memory monitoring apparatus is provided, which is applied to a terminal device of an android operating system, where an application program is installed in the android operating system, and the apparatus includes:
the reference unit is used for referencing Object objects in the application program in a PhantomReference mode in the application program and associating reference queue objects for the PhantomReference;
the starting unit is used for starting a monitoring thread for reading the ReferenceQueue object;
a reading unit, configured to read a pharma reference Object stored in the ReferenceQueue Object if the ReferenceQueue Object is not empty, and determine that an application program in which an Object referenced by the pharma reference Object is located has a garbage collection behavior when the pharma reference Object is successfully read;
and the determining unit is used for judging whether the used memory amount of the application program with the garbage collection behavior exceeds a threshold value or not, and if so, determining that the application program with the garbage collection behavior enters a low memory state.
Optionally, the apparatus further comprises:
and the recovery unit is used for adding the PhantomReference Object into the referenceQueue Object after the Object referenced by the PhantomReference Object is recovered by the garbage collector.
Optionally, the apparatus further comprises:
the release unit is used for recovering the memory resources occupied by the determined application program entering the low memory state; the recycled memory resource is a memory occupied by the running of unnecessary functions in the application program.
Optionally, the apparatus further comprises:
a blocking unit, for blocking the monitoring thread if the ReferenceQueue object is empty; and the monitoring thread is awakened after being updated by the ReferenceQueue object.
Optionally, after the reading unit, the apparatus further includes:
and the newly-built unit refers to the Object in the application program in a PhantomReference mode in the application program again, and associates a referenceQueue Object for the PhantomReference.
In a third aspect, an electronic device is provided, including:
a processor;
a memory for storing processor-executable instructions;
the processor is configured as the memory snooping method of any one of the above.
The embodiment of the application provides a memory monitoring scheme, and aims to timely determine that a low memory (low available memory) occurs in an application program APP running in an android operating system. Monitoring the occurrence of a garbage collector GC through a referenceQueue object and a Phantomreference object; because the GC triggers memory recovery only when the memory has pressure, the time for recovering the memory by the garbage recoverer GC is the most timely to trigger and monitor the APP memory, and whether the APP has low memory or not can be determined as soon as possible.
Drawings
Fig. 1 is a flowchart illustrating a memory snooping method according to an exemplary embodiment of the present application;
FIG. 2 is a schematic diagram illustrating an exemplary embodiment of the present application listening for GC occurrences;
fig. 3 is a hardware structure diagram of a memory snooping device according to an exemplary embodiment of the present application;
fig. 4 is a block diagram of a memory snoop device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The manner in which the following exemplary embodiments are described does not represent all manner of consistency with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
As mentioned above, google provides an android operating system without a low memory snoop and callback mechanism for APP level. The ubiquitous APP low memory monitoring requirement of android software developers cannot be met. Therefore, in the related art, it is often necessary to start a thread and sample the APP memory periodically. However, APP is not always in a low memory state; therefore, most of the time, the thread sampling is performed without work, and frequent sampling of the APP memory obviously occupies more system resources and affects system performance.
Therefore, the present application provides a scheme for triggering and monitoring the APP memory at the time when the garbage collector GC (garbage collection) recovers the memory, and specifically monitors the occurrence of the garbage collector GC through the ReferenceQueue object and the pharmacoreference object. Because the GC can trigger memory recovery only when the memory has pressure, the APP memory is monitored by triggering at the moment that the garbage collector GC recovers the memory most timely, and whether the APP has low memory or not can be determined at the fastest speed. In addition, the frequency of GC is not frequent, so the number of sampling APP memories in the embodiment of the present application is not large, and the embodiment of the present application does not occupy more system resources and affect the system performance.
Referring to a flowchart of a memory snooping method shown in fig. 1 in an exemplary embodiment of the present application, the method may be applied to a terminal device of an android operating system, where an android application is installed on the terminal device, and the method may specifically include the following steps:
step 110: referencing Object objects in an application program in a PhantomReference mode in the application program, and associating ReferenceQueue objects for the PhantomReference;
step 120: starting a monitoring thread for reading the ReferenceQueue object;
step 130: if the referenceQueue Object is not empty, reading a PhantomReference Object stored in the referenceQueue Object, and determining that garbage collection behavior occurs in an application program where an Object referenced by the PhantomReference Object is located when the PhantomReference Object is successfully read;
step 140: and judging whether the used memory amount of the application program with the garbage collection behavior exceeds a threshold value, and if so, determining that the application program with the garbage collection behavior enters a low memory state.
In an android operating system, when the memory has pressure, a GC mechanism is triggered, and part of the memory occupied by an application program is recycled by a GC. During the GC reclamation process, the memory of the reclaimed Object can be generally tracked by the PhantomReference Object.
PhantomReference is a reference in JAVA. The PhantomReference is mainly used for tracking the memory of the Object which is recycled by the garbage collector. The PhantomReference must be used in conjunction with a reference queue (ReferenceQueue).
Please refer to fig. 2 for a schematic diagram of the occurrence of the snoop GC.
As shown in fig. 2, when the GC is ready to recycle an Object, if it is found that a pharmacoreference Object is also referenced, and when the Object executes the final function, the virtual machine JVM adds the pharmacoreference Object to the ReferenceQueue Object associated therewith. Therefore, whether a memory is currently recycled can be judged by judging whether a PhantomReference object exists in the referenceQueue object or not.
For this purpose, the Object in the application program may be referred to in a pharmacoreference manner in the application program, and a ReferenceQueue Object is associated with the pharmacoreference Object.
And then starting a listening thread for reading the ReferenceQueue object.
The monitoring thread can be triggered by a ReferenceQueue object, and specifically, when a pharmaomreference object is newly added to the ReferenceQueue object, the monitoring thread can be awakened; so that the listening thread reads the updated ReferenceQueue object.
In another embodiment, the listening thread may periodically read the ReferenceQueue object.
There are two results of reading the ReferenceQueue object:
firstly, if the ReferenceQueue object is empty, it indicates that there is no memory recycled by the GC currently; and further blocking the monitoring thread, and waiting for being read again after being awakened next time.
Secondly, if the ReferenceQueue object is not empty, it indicates that a memory recycled by the GC currently exists; further, the PhantomReference object stored in the referenceQueue object can be read; the PhantomReference Object is used for storing references related to Object objects recycled by the garbage collector.
After the PhantomReference Object stored in the referenceQueue Object is read, determining that GC is generated in the application program where the Object referenced by the PhantomReference Object is located, and determining the used memory amount of the application program at this moment. If the used memory amount exceeds the threshold, it may be further determined that the application program enters a low memory state.
It should be noted that, after the PhantomReference object is read, the PhantomReference object is also recovered. At this time, the Object in the application program needs to be referred to in the application program in the manner of PhantomReference again. Thus, a newObject object is newly held in a virtual reference manner, so that the next GC occurrence can be monitored conveniently.
After the application program recycled by the GC is obtained, whether the application program has low memory risk or not can be judged by reading the memory use condition of the application program.
Specifically, the used memory amount of the application program in which the Object is read is compared with a threshold (the maximum available memory amount of the application program), and when the used memory amount exceeds the threshold, the application program can be determined to be a low-memory application program.
The process is described in detail below:
since the Object is internal to the application, there is an associative relationship between the application and the Object.
Since the Object is referred to by the PhantomReference Object, there is also an association between the Object and the PhantomReference Object.
Also because the PhantomReference object will be added to the referenceQueue object; therefore, an association relationship between the PhantomReference object and the referenceQueue object also exists.
From this, the association chain can be derived as: application program-Object-PhantomReference Object-referenceQueue Object.
When the application program generates GC, the Object of the application program is triggered to be recycled, and then the PhantomReference Object associated with the Object is added into the referenceQueue Object according to the reference relation. At this time, tracing can be performed based on the association chain:
a monitoring thread reads a PhantomReference object in a referenceQueue object;
acquiring an Object associated with the PhantomReference Object based on the reference relation;
positioning a target application program according to the application program of the Object;
then, it can be determined whether the memory is low or not according to the used memory amount of the target application program.
By the embodiment, the occurrence of the garbage collector GC is monitored by utilizing the referenceQueue object and the PhantomReference object in the application program; and then reading the memory use condition of the application program to judge whether the memory use condition is low. Because the GC can trigger memory recovery only when the memory has pressure, the APP memory is monitored by triggering at the moment that the garbage collector GC recovers the memory most timely, and whether the APP has low memory or not can be determined at the fastest speed.
The present application further provides the following embodiments for a determined low memory application:
recovering memory resources occupied by the determined application program entering the low memory state; the recycled memory resource is a memory occupied by the running of unnecessary functions in the application program.
For an application program in a low memory state, the used memory amount of the application program may exceed a threshold value at any time, so that OOM breakdown is caused; in order to avoid the occurrence of the OOM crash, the memory occupied by the low-memory application program needs to be recovered in time, so that the amount of the available memory reaches the safe range.
The reclaimed memory cannot be chosen at will because some memory is necessary for the application to run properly. When the functions necessary for normal operation are recovered, the abnormal exit of the application program can also be caused; this is clearly a default (ensuring that the application is running stably). Therefore, when selecting to reclaim the memory, it is necessary to preferentially reclaim the memory occupied by the operation of unnecessary functions in the application program. Therefore, the used memory amount is reduced, and the abnormal exit of the application program is avoided, so that the stable operation of the low-memory application program is realized.
Corresponding to the foregoing embodiments of the memory snooping method, the present application also provides embodiments of a memory snooping device.
The embodiment of the memory monitoring device can be applied to a server. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor in which the software implementation is located. In terms of hardware, as shown in fig. 3, a hardware structure diagram of the memory snoop apparatus of the present application is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 3, in an embodiment, other hardware may be included according to the actual memory snoop function, which is not described in detail herein.
Referring to fig. 4, in a software embodiment, the memory monitoring apparatus corresponds to the embodiment of fig. 1, and is applied to a terminal device of an android operating system, where an application program is installed in the android operating system; the memory snooping device may specifically include:
a reference unit 410, which references the Object in the application program in a pharma reference manner in the application program and associates a reference queue Object for the pharma reference;
a starting unit 420, configured to start a listening thread for reading the ReferenceQueue object;
a reading unit 430, configured to read a pharma reference Object stored in the ReferenceQueue Object if the ReferenceQueue Object is not empty, and determine that an application program in which an Object referenced by the pharma reference Object is located has a garbage collection behavior when the pharma reference Object is successfully read;
the determining unit 440 determines whether the used memory amount of the application program with the garbage collection behavior exceeds a threshold, and if so, determines that the application program with the garbage collection behavior enters a low memory state.
Optionally, the apparatus further comprises:
and the recovery unit is used for adding the PhantomReference Object into the referenceQueue Object after the Object referenced in the PhantomReference Object is recovered by the garbage collector.
Optionally, the apparatus further comprises:
the release unit is used for recovering the memory resources occupied by the determined application program entering the low memory state; the recycled memory resource is a memory occupied by the running of unnecessary functions in the application program.
Optionally, the apparatus further comprises:
a blocking unit, for blocking the monitoring thread if the ReferenceQueue object is empty; and the monitoring thread is awakened after being updated by the ReferenceQueue object.
Optionally, after the reading unit 430, the apparatus further includes:
and the newly-built unit refers to the Object in the application program in a PhantomReference mode in the application program again, and associates a referenceQueue Object for the PhantomReference.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
Fig. 4 above describes the internal functional modules and the structural schematic of the memory monitoring apparatus, and the substantial execution subject may be an electronic device, including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured as the memory snooping method of any one of the preceding.
In the above embodiments of the electronic device, it should be understood that the Processor may be a Central Processing Unit (CPU), other general-purpose processors, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, and the aforementioned memory may be a read-only memory (ROM), a Random Access Memory (RAM), a flash memory, a hard disk, or a solid state disk. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments can be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the embodiment of the electronic device, since it is substantially similar to the embodiment of the method, the description is simple, and for the relevant points, reference may be made to part of the description of the embodiment of the method.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (11)
1. A memory monitoring method is characterized by being applied to terminal equipment of an android operating system, wherein an application program is installed in the android operating system, and the method comprises the following steps:
referencing Object objects in an application program in a PhantomReference mode in the application program, and associating ReferenceQueue objects for the PhantomReference;
starting a monitoring thread for reading the ReferenceQueue object;
if the referenceQueue Object is not empty, reading a PhantomReference Object stored in the referenceQueue Object, and determining that garbage collection behavior occurs in an application program where an Object referenced by the PhantomReference Object is located when the PhantomReference Object is successfully read;
and judging whether the used memory amount of the application program with the garbage collection behavior exceeds a threshold value, and if so, determining that the application program with the garbage collection behavior enters a low memory state.
2. The method of claim 1, further comprising:
and after the Object referenced by the PhantomReference Object is recycled by a garbage collector, adding the PhantomReference Object into a referenceQueue Object.
3. The method of claim 1, further comprising:
recovering memory resources occupied by the determined application program entering the low memory state; the recycled memory resource is a memory occupied by the running of unnecessary functions in the application program.
4. The method of claim 1, further comprising:
if the ReferenceQueue object is empty, blocking the monitoring thread; and the monitoring thread is awakened after being updated by the ReferenceQueue object.
5. The method according to claim 1, wherein after determining that garbage collection is performed on the application program in which the Object referenced by the PhantomReference Object is located, the method further comprises:
and newly referencing the Object in the application program in a PhantomReference mode in the application program, and associating a referenceQueue Object for the PhantomReference.
6. The memory monitoring device is characterized in that the memory monitoring device is applied to terminal equipment of an android operating system, an application program is installed in the android operating system, and the memory monitoring device comprises:
the reference unit is used for referencing Object objects in the application program in a PhantomReference mode in the application program and associating reference queue objects for the PhantomReference;
the starting unit is used for starting a monitoring thread for reading the ReferenceQueue object;
a reading unit, configured to read a pharma reference Object stored in the ReferenceQueue Object if the ReferenceQueue Object is not empty, and determine that an application program in which an Object referenced by the pharma reference Object is located has a garbage collection behavior when the pharma reference Object is successfully read;
and the determining unit is used for judging whether the used memory amount of the application program with the garbage collection behavior exceeds a threshold value or not, and if so, determining that the application program with the garbage collection behavior enters a low memory state.
7. The apparatus of claim 6, further comprising:
and the recovery unit is used for adding the PhantomReference Object into the referenceQueue Object after the Object referenced by the PhantomReference Object is recovered by the garbage collector.
8. The apparatus of claim 6, further comprising:
the release unit is used for recovering the memory resources occupied by the determined application program entering the low memory state; the recycled memory resource is a memory occupied by the running of unnecessary functions in the application program.
9. The apparatus of claim 6, further comprising:
a blocking unit, for blocking the monitoring thread if the ReferenceQueue object is empty; and the monitoring thread is awakened after being updated by the ReferenceQueue object.
10. The method of claim 6, wherein after reading the cell, the apparatus further comprises:
and the newly-built unit refers to the Object in the application program in a PhantomReference mode in the application program again, and associates a referenceQueue Object for the PhantomReference.
11. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
the processor is configured as the method of any of the above claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010365031.2A CN111552616A (en) | 2020-04-30 | 2020-04-30 | Memory monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010365031.2A CN111552616A (en) | 2020-04-30 | 2020-04-30 | Memory monitoring method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111552616A true CN111552616A (en) | 2020-08-18 |
Family
ID=72004264
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010365031.2A Withdrawn CN111552616A (en) | 2020-04-30 | 2020-04-30 | Memory monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552616A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112433809A (en) * | 2020-11-05 | 2021-03-02 | 北京浪潮数据技术有限公司 | JVM memory management method, device, equipment and readable storage medium |
| CN112650695A (en) * | 2020-12-30 | 2021-04-13 | 北京奇艺世纪科技有限公司 | Cache management method and device of application server |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070203960A1 (en) * | 2006-02-26 | 2007-08-30 | Mingnan Guo | System and method for computer automatic memory management |
| CN105302714A (en) * | 2014-07-24 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Method and apparatus for monitoring memory leak in test process |
| CN106844159A (en) * | 2017-02-03 | 2017-06-13 | 广东欧珀移动通信有限公司 | A kind of information acquisition method, device and intelligent terminal |
| CN107239394A (en) * | 2016-03-29 | 2017-10-10 | 卓望数码技术（深圳）有限公司 | A kind of method for detecting memory leakage and device of Android application |
| CN108073439A (en) * | 2016-11-11 | 2018-05-25 | 深圳业拓讯通信科技有限公司 | A kind of JVM RAM leakages automatic testing method and system |
| WO2018099163A1 (en) * | 2016-11-30 | 2018-06-07 | 西安中兴新软件有限责任公司 | Terminal and application control method |
| CN109558308A (en) * | 2018-09-29 | 2019-04-02 | 中国平安人寿保险股份有限公司 | Application program method for detecting memory leakage, device, electronic equipment and storage medium |
| CN109697036A (en) * | 2018-12-29 | 2019-04-30 | 北京金山安全软件有限公司 | Information processing method and device |
-
2020
- 2020-04-30 CN CN202010365031.2A patent/CN111552616A/en not_active Withdrawn
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070203960A1 (en) * | 2006-02-26 | 2007-08-30 | Mingnan Guo | System and method for computer automatic memory management |
| CN105302714A (en) * | 2014-07-24 | 2016-02-03 | 腾讯科技（深圳）有限公司 | Method and apparatus for monitoring memory leak in test process |
| CN107239394A (en) * | 2016-03-29 | 2017-10-10 | 卓望数码技术（深圳）有限公司 | A kind of method for detecting memory leakage and device of Android application |
| CN108073439A (en) * | 2016-11-11 | 2018-05-25 | 深圳业拓讯通信科技有限公司 | A kind of JVM RAM leakages automatic testing method and system |
| WO2018099163A1 (en) * | 2016-11-30 | 2018-06-07 | 西安中兴新软件有限责任公司 | Terminal and application control method |
| CN106844159A (en) * | 2017-02-03 | 2017-06-13 | 广东欧珀移动通信有限公司 | A kind of information acquisition method, device and intelligent terminal |
| CN109558308A (en) * | 2018-09-29 | 2019-04-02 | 中国平安人寿保险股份有限公司 | Application program method for detecting memory leakage, device, electronic equipment and storage medium |
| CN109697036A (en) * | 2018-12-29 | 2019-04-30 | 北京金山安全软件有限公司 | Information processing method and device |
Non-Patent Citations (2)
| Title |
|---|
| 张昊;潘祖烈;: "Java软引用防止内存泄漏技术的研究" * |
| 王伟民: "谈谈Java程序中的内存渗漏" * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112433809A (en) * | 2020-11-05 | 2021-03-02 | 北京浪潮数据技术有限公司 | JVM memory management method, device, equipment and readable storage medium |
| CN112433809B (en) * | 2020-11-05 | 2023-12-22 | 北京浪潮数据技术有限公司 | JVM memory management method, device, equipment and readable storage medium |
| CN112650695A (en) * | 2020-12-30 | 2021-04-13 | 北京奇艺世纪科技有限公司 | Cache management method and device of application server |
| CN112650695B (en) * | 2020-12-30 | 2023-09-05 | 北京奇艺世纪科技有限公司 | Cache management method and device of application server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101983413B1 (en) | Managing object lifetime in a cyclic graph | |
| WO2018072408A1 (en) | Memory analysis method, device, system and computing device | |
| US7458078B2 (en) | Apparatus and method for autonomic hardware assisted thread stack tracking | |
| KR101174751B1 (en) | Malware auto-analysis system and method using kernel call-back mechanism | |
| US7765528B2 (en) | Identifying sources of memory retention | |
| US20070136402A1 (en) | Automatic prediction of future out of memory exceptions in a garbage collected virtual machine | |
| US6951015B2 (en) | Prefetch insertion by correlation of cache misses and previously executed instructions | |
| US20060253498A1 (en) | Method and apparatus for reclaiming memory from a heap | |
| KR101438990B1 (en) | System testing method | |
| CN111552616A (en) | Memory monitoring method and device | |
| CN108664390B (en) | Memory leak detection method and equipment | |
| US20060253503A1 (en) | Method and apparatus for aging a versioned heap system | |
| JP5212357B2 (en) | Multi-CPU abnormality detection and recovery system, method and program | |
| CN111625833A (en) | Efficient method and device for judging reuse vulnerability after software program release | |
| CN111209164A (en) | Abnormal information storage method and device, electronic equipment and storage medium | |
| CN108279993B (en) | Method and device for realizing service degradation and electronic equipment | |
| CN112214378B (en) | Data collection method and device, electronic equipment and storage medium | |
| CN112035253B (en) | Linux system page cache recovery method and related device | |
| US10783027B2 (en) | Preemptive crash data capture | |
| CN110704313A (en) | Memory leakage detection method and device for JAVA virtual machine | |
| CN113064765B (en) | Node exception handling method, device, electronic equipment and machine-readable storage medium | |
| JP2012123762A (en) | Information processing device and information processing method | |
| CN113312623B (en) | Process detection method and device in access control, electronic equipment and storage medium | |
| CN112269768A (en) | Page cache recovery method, device, equipment and storage medium | |
| CN111857689A (en) | Framework, function configuration method of framework, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200818 |
|
| WW01 | Invention patent application withdrawn after publication |