CN106598725A - Android-based Handler memory leakage prevention device and method - Google Patents
Android-based Handler memory leakage prevention device and method Download PDFInfo
- Publication number
- CN106598725A CN106598725A CN201610929424.5A CN201610929424A CN106598725A CN 106598725 A CN106598725 A CN 106598725A CN 201610929424 A CN201610929424 A CN 201610929424A CN 106598725 A CN106598725 A CN 106598725A
- Authority
- CN
- China
- Prior art keywords
- message
- runnable
- asynchronous
- thread
- requests
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
- G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides an Android-based Handler memory leakage prevention device comprising: an asynchronous Runnable request receiving module used for receiving Runnable requests of asynchronous tasks; a synchronizing module used for synchronizing all received Runnable requests of the asynchronous tasks by adopting a weak quotation method; an asynchronous request execution module used for executing the Runnable requests of the asynchronous tasks and judging whether a message needs to be sent; a sub-line thread execution termination module used for terminating a sub-line thread if there is no message to be sent; a message sending module used for sending a message and a weak quotation relationship between the message and an asynchronous thread when the message needs to be sent; and a message distribution module used for storing the message and the weak quotation relationship between the message and the asynchronous thread and sending the same to a main thread for processing according to the time sequence of the message. According to the Android-based Handler memory leakage prevention device provided by the invention, the weak quotation relationship is introduced to ensure that resources can be smoothly recycled by a garbage collector, and no memory leakage is generated in the case of normal communication of the sub-thread and the main thread.
Description
Technical field
The invention belongs to android system security fields, and in particular to a kind of anti-internal memory of the Handler based on Android
Leakage device and method.
Background technology
More or less can be using to multithreading, when using multithreading in Android software exploitation
Just there is the extraction of a problem points, that is, how sub-line journey and main thread are communicated.Android is we provided
One relatively good instrument Handler, by Handler, this instrument sends messages to main thread, main line in sub-line journey
Journey is received after the message of sub-line journey, and according to the different type of message different operations can be done.
That is Handler mainly causes main thread and sub-line journey to be communicated by message mechanism.Handler
This message mechanism solves the problems, such as that sub-line journey and main thread communicate really, but but another potential risks, using upper
Slightly do not note the risk for being possible to that memory overflow can be caused.
Memory overflow any problem can be brought to system.Internal memory is belonging in itself the nervous resource of comparison on mobile phone, interior
It is limited to deposit resource, and what memory overflow referred to is exactly that those were once used, the resource do not used now, not and
When discharge the partial memory, and the part resource exists always in internal memory, and this block region can neither be using also will not being released
Put.Because this block internal memory is occupied always and can not be timely released, so causing to need to apply for interior again in the case of other
But apply that system card just occurs less than enough memory headrooms when depositing, it is possible that application crashes etc. when serious
Consequence.As can be seen here memory overflow brings very bad result to us.
The content of the invention
The technical problem to be solved in the present invention is：There is provided a kind of anti-memory overflow device of the Handler based on Android and
Method, avoids the leakage of internal memory on the premise of sub-line journey and main thread proper communication.
The present invention is for the solution technical scheme taken of above-mentioned technical problem：A kind of Handler based on Android prevents
Memory overflow device, it is characterised in that：It includes：
Asynchronous Runnable request receiving modules, the Runnable for receiving asynchronous task is asked；
Synchronization module, for synchronously preserving the Runnable requests of all asynchronous tasks for receiving using weak reference method；
Asynchronous Request performing module, the Runnable for performing asynchronous task is asked, and determines whether that message will send；
Sub-line thread performs terminate module, for when to send without message, terminating sub-line thread；
Message transmission module, for when there is message to send, sending the weak reference relation of message and message and asynchronous thread；
Message distribution module is for storing the weak reference relation of message and message and asynchronous thread and suitable according to the time of message
Sequence is sent to main thread process.
By said apparatus, doubly linked list is included in described synchronization module, for storing described asynchronous task
Runnable is asked.
By said apparatus, the priority of the thread that is also stored with described synchronization module is different for removing according to priority
The Runnable requests of step task.
By said apparatus, lock module is included in described synchronization module, for realizing synchronous preservation；Lock module includes：
Lock acquisition module, during for asking in the Runnable for receiving new asynchronous task, obtains the proprietary rightss of lock；
Operation module, deposits for the Runnable requests when the proprietary rightss of lock are got to described new asynchronous task
Storage removes operation；
Lock release module, for when storing or removal operation is completed, discharging the proprietary rightss of lock.
By said apparatus, described message includes timely message and delay message；
Message queue and intervalometer are provided with described message distribution module；Described intervalometer is used for timing, when intervalometer surpasses
When after delay message is sent in message queue；Described timely message is put directly into message queue；Described message team
Arrange the orderly main thread that is sent to of the sequencing for entering according to message to process.
A kind of anti-memory overflow method of the Handler based on Android, it is characterised in that：It is comprised the following steps：
Receive the Runnable requests of asynchronous task；
The Runnable requests of all asynchronous tasks for receiving synchronously are preserved using weak reference method；
The Runnable requests of asynchronous task are performed, determines whether that message will send；
When to send without message, terminate sub-line thread；
When there is message to send, the weak reference relation of message and message and asynchronous thread is sent；
The weak reference relation of message and message and asynchronous thread is stored, and the time sequencing according to message is sent at main thread
Reason.
As stated above, the Runnable requests of described asynchronous task are stored by the way of doubly linked list.
As stated above, after storing the Runnable requests of described asynchronous task, according to priority asynchronous task is removed
Runnable request.
As stated above, realize that the synchronous concrete mode for preserving is：
When the Runnable for receiving new asynchronous task is asked, the proprietary rightss of lock are obtained；
Runnable requests when the proprietary rightss of lock are got to described new asynchronous task are stored or are removed operation；
When storing or removal operation is completed, the proprietary rightss of lock are discharged.
As stated above, described message includes timely message and delay message；
Message queue and intervalometer are provided with this method；When the timer times out delay message is sent in message queue afterwards；Institute
The timely message stated is put directly into message queue；Message queue according to the sequencing that message is entered it is orderly be sent to main line
Journey process.
Beneficial effects of the present invention are：
1st, in the Runnable requests and transmission message for storing asynchronous task, by the way of weak reference, weak reference is maximum
Advantage be that Garbage Collector can automatically go the resource for reclaiming weak reference, therefore weak reference when system resource is nervous
The introducing of relation, it is ensured that resource can be reclaimed smoothly by Garbage Collector, sub-line journey and main thread proper communication
Under the premise of guarantee problem that memory overflow will not occur, so as to fundamentally prevent the generation of memory leak issue.
2nd, the Runnable requests of asynchronous task are stored by way of using doubly linked list, using doubly linked list " right
What is mainly changed when data are modified is pointer rather than data itself " this exclusive characteristic, being capable of quick logarithm
According to being deleted and being increased, efficiency is improved.
3rd, by carrying out staged care to thread, the task of high priority can be fully ensured that to urgent by priority treatment
Task carries out priority scheduling.
4th, certain process has been done in the distribution to message.
Description of the drawings
Fig. 1 is the method flow diagram of one embodiment of the invention.
Fig. 2 is the synchronous method flow diagram for preserving.
Specific embodiment
Explanation of nouns：
Handler：The instrument that a set of main thread and sub-line journey that android system is provided is communicated
Memory overflow：Memory overflow is also referred to as " storage seepage ", and the space opened up with dynamic memory partition function dynamic is using
Do not discharge after finishing, as a result cause to occupy the internal storage location always.Until EP (end of program).（It is exactly plainly in fact that the internal memory is empty
Between using unrecovered after finishing）I.e. so-called memory overflow.
：There can be two ways to realize multithreading in java, one kind is to inherit Thread classes, and one kind is to realize Runnable
Interface.Runnable is a kind of form of expression of multithreading.
Garbage Collector：It is a set of garbage collection algorithms of Java Virtual Machine offer, it is useless in the regular recovery system of meeting
Garbage object carrys out releasing memory space.
With reference to instantiation and accompanying drawing, the present invention is described further.
Embodiment one：
The present embodiment provides a kind of anti-memory overflow devices of Handler based on Android, and it includes：Asynchronous Runnable please
Receiver module is sought, the Runnable for receiving asynchronous task is asked.Synchronization module, for synchronously being preserved using weak reference method
The Runnable requests of all asynchronous tasks for receiving.Asynchronous Request performing module, for performing asynchronous task
Runnable is asked, and determines whether that message will send；Sub-line thread performs terminate module, for send without message
When, terminate sub-line thread.Message transmission module, for when there is message to send, sending message and message with asynchronous thread
Weak reference relation.Message distribution module, for storing the weak reference relation of message and message and asynchronous thread, and according to message
Time sequencing is sent to main thread process.
A kind of anti-memory overflow method of the Handler based on Android, as shown in figure 1, comprising the following steps：
S1, the Runnable requests for receiving asynchronous task.
S2, the Runnable requests that all asynchronous tasks for receiving synchronously are preserved using weak reference method.
Weak reference is an instrument in Java, and the relation between object under default situations in Java language is strongly reference
Relation.The occupation mode of weak reference is that object is modified using keyword WeakReference（For example
WeakReference<Date> mDate）, just there is weak reference and close with such through the object of WeakReference modifieds
It is.The maximum difference of weak reference and strongly reference relation is：
1）If there is any other resource to hold adduction relationship so rubbish to it after working as memory source use for strongly reference
Rubbish withdrawer just cannot be reclaimed to the resource.
2）For weak reference also wants in time other resources to hold adduction relationship to it after memory source use, rubbish is returned
Receive when device internally deposits into row recovery and find that the object has been labeled as weak reference relation, then Garbage Collector still meeting
It is recycled.
S3, the Runnable requests for performing asynchronous task, determine whether that message will send.
Taking out the Runnable requests of asynchronous task carries out execution process.If returned without any message in asynchronous task
Return, then directly process and complete, will not any process information of outer layers transmission.If asynchronous thread needs outwardly to send disappeared
When breath this when asynchronous task can to main thread send message.
S4, without message to send when, terminate sub-line thread.
S5, when there is message to send, send the weak reference relation of message and message and asynchronous thread.
Now because asynchronous task needs to send message, there is adduction relationship between asynchronous task and message.Cause
Process to be possible to message may require that for a long time, message can be caused this when to hold asynchronous thread so as to asynchronous thread without
Method carries out recuperability, thus this place we design when used weak reference WeakReference to keep away
Exempt from the generation of the problems referred to above, even if message has not processed thread resources and still can have been reclaimed by system rubbish withdrawer.
Because processing the relation between message and thread using weak reference, thus by the connection between message and thread
System's " dying down ", facilitates garbage reclamation mechanism to carry out reclaiming in the whole system term of execution.
The weak reference relation of S6, storage message and message and asynchronous thread, and the time sequencing according to message is sent to master
Thread process.
To after main thread, main thread can make corresponding process to corresponding message for S7, message distribution.Herein concrete
Process just related to specific service logic, such as sub-line journey is downloaded to complete to be needed to refresh main thread UI etc..（This step is
Optional step, being merely to illustrate message distribution has carried out what kind of process, and the core of non-invention to after main thread）
There are 2 places to use weak reference relation in the global design of the present embodiment, one is that thread and sets of threads are used
Weak reference relation, another is that weak reference relation has been used between thread and message.Because the use of weak reference relation, makes
Obtaining Garbage Collector can reasonably be reclaimed when corresponding to resource, be not in that chaotic adduction relationship causes nothing
The problem that method is reclaimed.Weak reference is arrived used in the present embodiment, Garbage Collector can be reclaimed periodically to rubbish, so without
Releasing memory is gone manually every time, without the problem points for worrying RAM leakage again.
Embodiment two：
The present embodiment on the basis of embodiment one, device：Doubly linked list is set in synchronization module, it is described different for storing
The Runnable requests of step task.Method：The Runnable requests of described asynchronous task are stored by the way of doubly linked list.
Each back end of doubly linked list is comprising the adduction relationship prior to previous node and to latter section
The adduction relationship next of point.Only first node and last node have some it is special where.First node
Prior is sky, because first node does not go up a node.The next of last node is sky, because last section
Point is without following node data.Other all nodes all have prior and next information to preserve.Why using two-way
Storing all asynchronous tasks, main cause is the exclusive characteristic of doubly linked list to chained list, quickly data can be carried out deleting and
Increase, also in that having this characteristic so we have selected doubly linked list data asynchronous task set is entered when design
Row management.Why quickly data can be increased and are deleted, be because doubly linked list data are modified when
Wait main change is pointer rather than data itself, so can be very efficient for the change of data.
Embodiment three：
The present embodiment on the basis of embodiment one or two, device：Also be stored with the priority of thread in synchronization module, for pressing
The Runnable requests of asynchronous task are removed according to priority.Method：After the Runnable requests of the described asynchronous task of storage, press
The Runnable requests of asynchronous task are removed according to priority.So the task of high priority can be by priority treatment.Energy after classification
It is enough to ensure to carry out priority scheduling to hot job.
Example IV：
The present embodiment on the basis of embodiment one or two, device：Lock module is included in synchronization module, for realizing synchronous guarantor
Deposit；Lock module includes：Lock acquisition module, during for asking in the Runnable for receiving new asynchronous task, obtains the institute of lock
Have the right；Operation module, is carried out for the Runnable requests when the proprietary rightss of lock are got to described new asynchronous task
Storage removes operation；Lock release module, for when storing or removal operation is completed, discharging the proprietary rightss of lock.
Method：Realize that the synchronous concrete mode for preserving is as shown in Figure 2：
S201, receive new asynchronous task Runnable ask when, obtain lock proprietary rightss；
If S202, the proprietary rightss failure for obtaining lock, continuous poll is reacquired；
S203, the Runnable requests when the proprietary rightss of lock are got to described new asynchronous task are stored or removed
Operation；
S204, store or remove operation complete when, discharge lock proprietary rightss.
Lock acquiescence only one of which is provided with whole system, so also ensures that any moment there can only be a thread to obtain
Lock resource is got, the storage and removal that so can ensure that the Runnable requests of asynchronous task synchronously completes process.
After the completion of the storage that the Runnable of asynchronous task is asked and removing operation execution, need to discharge lock power immediately
Limit, lock resource is discharged, and can so facilitate other thread to carry out locking the acquisition of resource.It is certain herein to need to lock
Resource is discharged, and is only released lock resource other threads and can again be obtained lock and performs flow process below.
Embodiment five：
The present embodiment on the basis of embodiment one, device：Described message includes timely message and delay message；Described disappears
Message queue and intervalometer are provided with breath distribution module；Described intervalometer is used for timing, when the timer times out time delay disappears afterwards
Breath is sent in message queue；Described timely message is put directly into message queue；Described message queue is used for according to disappearing
The main thread that is sent to that the sequencing of breath entrance is orderly is processed.
Method：It is provided with message queue and intervalometer；When the timer times out delay message is sent in message queue afterwards；Institute
The timely message stated is put directly into message queue；Message queue according to the sequencing that message is entered it is orderly be sent to main line
Journey process.
By the classification to message, so as to carry out the distribution of temporal logic to different message, message is further increased
The high efficiency of process.
Above example is merely to illustrate the design philosophy and feature of the present invention, its object is to make technology in the art
Personnel will appreciate that present disclosure and implement according to this that protection scope of the present invention is not limited to above-described embodiment.It should be emphasized that
, embodiment two to embodiment five is preferred version, wherein the superposition of any one embodiment or several embodiments should also be as
Belong to protection scope of the present invention.Also, all equivalent variations made according to disclosed principle, mentality of designing are repaiied
Decorations, within protection scope of the present invention.
Claims (10)
1. anti-memory overflow devices of a kind of Handler based on Android, it is characterised in that：It includes：
Asynchronous Runnable request receiving modules, the Runnable for receiving asynchronous task is asked；
Synchronization module, for synchronously preserving the Runnable requests of all asynchronous tasks for receiving using weak reference method；
Asynchronous Request performing module, the Runnable for performing asynchronous task is asked, and determines whether that message will send；
Sub-line thread performs terminate module, for when to send without message, terminating sub-line thread；
Message transmission module, for when there is message to send, sending the weak reference relation of message and message and asynchronous thread；
Message distribution module is for storing the weak reference relation of message and message and asynchronous thread and suitable according to the time of message
Sequence is sent to main thread process.
2. anti-memory overflow devices of a kind of Handler based on Android according to claim 1, it is characterised in that：Institute
Doubly linked list is included in the synchronization module stated, for storing the Runnable requests of described asynchronous task.
3. a kind of anti-memory overflow devices of Handler based on Android according to claim 1 and 2, its feature exists
In：Also be stored with the priority of thread in described synchronization module, for removing the Runnable of asynchronous task according to priority
Request.
4. a kind of anti-memory overflow devices of Handler based on Android according to claim 1 and 2, its feature exists
In：Lock module is included in described synchronization module, for realizing synchronous preservation；Lock module includes：
Lock acquisition module, during for asking in the Runnable for receiving new asynchronous task, obtains the proprietary rightss of lock；
Operation module, deposits for the Runnable requests when the proprietary rightss of lock are got to described new asynchronous task
Storage removes operation；
Lock release module, for when storing or removal operation is completed, discharging the proprietary rightss of lock.
5. anti-memory overflow devices of a kind of Handler based on Android according to claim 1, it is characterised in that：Institute
The message stated includes timely message and delay message；
Message queue and intervalometer are provided with described message distribution module；Described intervalometer is used for timing, when intervalometer surpasses
When after delay message is sent in message queue；Described timely message is put directly into message queue；Described message team
Arrange the orderly main thread that is sent to of the sequencing for entering according to message to process.
6. a kind of anti-memory overflow methods of Handler based on Android, it is characterised in that：It is comprised the following steps：
Receive the Runnable requests of asynchronous task；
The Runnable requests of all asynchronous tasks for receiving synchronously are preserved using weak reference method；
The Runnable requests of asynchronous task are performed, determines whether that message will send；
When to send without message, terminate sub-line thread；
When there is message to send, the weak reference relation of message and message and asynchronous thread is sent；
The weak reference relation of message and message and asynchronous thread is stored, and the time sequencing according to message is sent at main thread
Reason.
7. anti-memory overflow methods of a kind of Handler based on Android according to claim 1, it is characterised in that：Adopt
The Runnable requests of described asynchronous task are stored with the mode of doubly linked list.
8. a kind of anti-memory overflow methods of Handler based on Android according to claim 6 or 7, its feature exists
In：After the Runnable requests of the described asynchronous task of storage, according to priority the Runnable requests of asynchronous task are removed.
9. a kind of anti-memory overflow methods of Handler based on Android according to claim 6 or 7, its feature exists
In：Realize that the synchronous concrete mode for preserving is：
When the Runnable for receiving new asynchronous task is asked, the proprietary rightss of lock are obtained；
Runnable requests when the proprietary rightss of lock are got to described new asynchronous task are stored or are removed operation；
When storing or removal operation is completed, the proprietary rightss of lock are discharged.
10. anti-memory overflow methods of a kind of Handler based on Android according to claim 6, it is characterised in that：
Described message includes timely message and delay message；
Message queue and intervalometer are provided with this method；When the timer times out delay message is sent in message queue afterwards；Institute
The timely message stated is put directly into message queue；Message queue according to the sequencing that message is entered it is orderly be sent to main line
Journey process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610929424.5A CN106598725A (en) | 2016-10-31 | 2016-10-31 | Android-based Handler memory leakage prevention device and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610929424.5A CN106598725A (en) | 2016-10-31 | 2016-10-31 | Android-based Handler memory leakage prevention device and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106598725A true CN106598725A (en) | 2017-04-26 |
Family
ID=58556455
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610929424.5A Pending CN106598725A (en) | 2016-10-31 | 2016-10-31 | Android-based Handler memory leakage prevention device and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106598725A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107015866A (en) * | 2017-03-23 | 2017-08-04 | 腾讯科技（深圳）有限公司 | A kind of data processing method and device |
| CN107291598A (en) * | 2017-08-07 | 2017-10-24 | 腾讯科技（深圳）有限公司 | Monitoring method, supervising device, monitoring device and storage medium |
| CN107515792A (en) * | 2017-07-27 | 2017-12-26 | 北京五八信息技术有限公司 | The method and apparatus that function class carries out Message Processing using Handler |
| CN107818023A (en) * | 2017-11-06 | 2018-03-20 | 深圳市雷鸟信息科技有限公司 | Thread-based message processing method, intelligent device and storage medium |
| CN108008950A (en) * | 2017-11-24 | 2018-05-08 | 武汉斗鱼网络科技有限公司 | The implementation method and device of a kind of user interface updating |
| CN109062689A (en) * | 2018-07-17 | 2018-12-21 | 武汉斗鱼网络科技有限公司 | Method, storage medium, electronic equipment and the system of automatic releasing document resource |
| CN109246177A (en) * | 2018-07-04 | 2019-01-18 | 武汉斗鱼网络科技有限公司 | Asynchronous communication tool design method in Android |
| CN109347996A (en) * | 2018-12-10 | 2019-02-15 | 中共中央办公厅电子科技学院 | A kind of DNS domain name acquisition system and method |
| CN109800783A (en) * | 2018-12-11 | 2019-05-24 | 中新金桥数字科技(北京)有限公司 | The method and its system of super large picture superposition comparison are realized based on Android Pad |
| CN110647405A (en) * | 2018-06-27 | 2020-01-03 | 北京京东尚科信息技术有限公司 | System message processing method, electronic device, and computer-readable storage medium |
| CN110806867A (en) * | 2018-08-06 | 2020-02-18 | 武汉斗鱼网络科技有限公司 | Handle management method, storage medium, electronic device and system |
| CN112015395A (en) * | 2020-08-28 | 2020-12-01 | 中移（杭州）信息技术有限公司 | Method and device for preventing memory leakage and computer readable storage medium |
| CN112416623A (en) * | 2020-11-27 | 2021-02-26 | 宝能(广州)汽车研究院有限公司 | Message delivery method for android system and computer-readable storage medium |
| WO2021147382A1 (en) * | 2020-01-21 | 2021-07-29 | 上海万物新生环保科技集团有限公司 | Test task execution method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6711739B1 (en) * | 1999-11-08 | 2004-03-23 | Sun Microsystems, Inc. | System and method for handling threads of execution |
| CN101727355A (en) * | 2008-10-31 | 2010-06-09 | 国际商业机器公司 | Handling method and system for memory access events |
| US7756911B2 (en) * | 2006-06-09 | 2010-07-13 | International Business Machines Corporation | Method and system for executing a task and medium storing a program therefor |
| CN102999386A (en) * | 2012-11-08 | 2013-03-27 | 山东大学 | Method for achieving multi-message queue mechanism to improve performance in single process |
| CN104423996A (en) * | 2013-09-04 | 2015-03-18 | 腾讯科技（深圳）有限公司 | View refreshing method and view refreshing device |
| CN104834544A (en) * | 2015-05-04 | 2015-08-12 | 广州杰赛科技股份有限公司 | Data loading method and device |
-
2016
- 2016-10-31 CN CN201610929424.5A patent/CN106598725A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6711739B1 (en) * | 1999-11-08 | 2004-03-23 | Sun Microsystems, Inc. | System and method for handling threads of execution |
| US7756911B2 (en) * | 2006-06-09 | 2010-07-13 | International Business Machines Corporation | Method and system for executing a task and medium storing a program therefor |
| CN101727355A (en) * | 2008-10-31 | 2010-06-09 | 国际商业机器公司 | Handling method and system for memory access events |
| CN102999386A (en) * | 2012-11-08 | 2013-03-27 | 山东大学 | Method for achieving multi-message queue mechanism to improve performance in single process |
| CN104423996A (en) * | 2013-09-04 | 2015-03-18 | 腾讯科技（深圳）有限公司 | View refreshing method and view refreshing device |
| CN104834544A (en) * | 2015-05-04 | 2015-08-12 | 广州杰赛科技股份有限公司 | Data loading method and device |
Non-Patent Citations (2)
| Title |
|---|
| 张帆: "《java范例开发大全》", 30 June 2010, 清华大学出版社 * |
| 高林: "基于Android智能终端信息采集系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107015866A (en) * | 2017-03-23 | 2017-08-04 | 腾讯科技（深圳）有限公司 | A kind of data processing method and device |
| CN107515792A (en) * | 2017-07-27 | 2017-12-26 | 北京五八信息技术有限公司 | The method and apparatus that function class carries out Message Processing using Handler |
| CN107515792B (en) * | 2017-07-27 | 2020-11-10 | 北京五八信息技术有限公司 | Method and device for processing message by using function class Handler |
| CN107291598A (en) * | 2017-08-07 | 2017-10-24 | 腾讯科技（深圳）有限公司 | Monitoring method, supervising device, monitoring device and storage medium |
| CN107291598B (en) * | 2017-08-07 | 2018-07-06 | 腾讯科技（深圳）有限公司 | Monitoring method, monitoring device, monitoring device and storage medium |
| CN107818023A (en) * | 2017-11-06 | 2018-03-20 | 深圳市雷鸟信息科技有限公司 | Thread-based message processing method, intelligent device and storage medium |
| CN107818023B (en) * | 2017-11-06 | 2021-06-15 | 深圳市雷鸟网络传媒有限公司 | Thread-based message processing method, intelligent device and storage medium |
| CN108008950A (en) * | 2017-11-24 | 2018-05-08 | 武汉斗鱼网络科技有限公司 | The implementation method and device of a kind of user interface updating |
| CN110647405A (en) * | 2018-06-27 | 2020-01-03 | 北京京东尚科信息技术有限公司 | System message processing method, electronic device, and computer-readable storage medium |
| CN109246177A (en) * | 2018-07-04 | 2019-01-18 | 武汉斗鱼网络科技有限公司 | Asynchronous communication tool design method in Android |
| CN109246177B (en) * | 2018-07-04 | 2021-04-27 | 武汉斗鱼网络科技有限公司 | Method for designing asynchronous communication tool in Android |
| CN109062689B (en) * | 2018-07-17 | 2020-07-31 | 武汉斗鱼网络科技有限公司 | Method, storage medium, electronic device and system for automatically releasing file resources |
| CN109062689A (en) * | 2018-07-17 | 2018-12-21 | 武汉斗鱼网络科技有限公司 | Method, storage medium, electronic equipment and the system of automatic releasing document resource |
| CN110806867A (en) * | 2018-08-06 | 2020-02-18 | 武汉斗鱼网络科技有限公司 | Handle management method, storage medium, electronic device and system |
| CN110806867B (en) * | 2018-08-06 | 2022-06-17 | 武汉斗鱼网络科技有限公司 | Handle management method, storage medium, electronic device and system |
| CN109347996A (en) * | 2018-12-10 | 2019-02-15 | 中共中央办公厅电子科技学院 | A kind of DNS domain name acquisition system and method |
| CN109800783A (en) * | 2018-12-11 | 2019-05-24 | 中新金桥数字科技(北京)有限公司 | The method and its system of super large picture superposition comparison are realized based on Android Pad |
| WO2021147382A1 (en) * | 2020-01-21 | 2021-07-29 | 上海万物新生环保科技集团有限公司 | Test task execution method and device |
| CN112015395A (en) * | 2020-08-28 | 2020-12-01 | 中移（杭州）信息技术有限公司 | Method and device for preventing memory leakage and computer readable storage medium |
| CN112416623A (en) * | 2020-11-27 | 2021-02-26 | 宝能(广州)汽车研究院有限公司 | Message delivery method for android system and computer-readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106598725A (en) | Android-based Handler memory leakage prevention device and method | |
| CN106802826B (en) | Service processing method and device based on thread pool | |
| CN106547612B (en) | Multitasking method and device | |
| CN109783229A (en) | The method and device of thread resources distribution | |
| CN103514102B (en) | A kind of Java Virtual Machine realizes the method and device of internal memory garbage reclamation | |
| CN104216767B (en) | The method and device of accessing shared data between multithreading | |
| CN107181789A (en) | A kind of distributed lock implementation method and device | |
| CN108399094B (en) | Application deployment method, deployment device thereof and edge data center | |
| CN107515785A (en) | A kind of EMS memory management process and device | |
| CN104461707A (en) | Locking request processing method and device | |
| CN101477386B (en) | Timer implementing method and apparatus | |
| CN102207890A (en) | Task information processing method and scheduling control processing device | |
| CN103257700B (en) | The power-economizing method of a kind of android system and device | |
| CN107357630A (en) | A kind of method, apparatus and storage medium for realizing that virtual machine is synchronous | |
| CN110471774A (en) | A kind of data processing method and device based on unified task schedule | |
| CN112286688A (en) | Memory management and use method, device, equipment and medium | |
| CN107766125A (en) | A kind of delet method of cloud platform virtual machine | |
| CN113051049B (en) | Task scheduling system, method, electronic device and readable storage medium | |
| CN114579323A (en) | Thread processing method, device, equipment and medium | |
| CN110442530A (en) | The method of memory optimization data processing, storage medium | |
| CN111597035B (en) | Simulation engine time propulsion method and system based on multithreading | |
| CN101189579A (en) | Behavioral model based multi-threaded architecture | |
| CN112346848A (en) | Method, device and terminal for managing memory pool | |
| CN110543357B (en) | Method, related device and system for managing application program object | |
| CN105549911B (en) | The data transmission method and device of NVRAM |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170426 |