Method and device for message processing by function class using handler

Abstract

The embodiment of the invention provides a method and a device for using Handler to carry out message processing by a function class. The method for using the Handler to carry out the message processing by the function class comprises the following steps that: a function class receives a business processing request message; and the function class processes the business processing request message through a first Handler class and a second Handler class, wherein the second Handler class weakly cites the first Handler class, and the second Handler class is a native Handler subclass. By use of the embodiment of the invention, in a simple way, a reachable path from the native Handler to the function class is weak reachability, the problem of function class OOM (Out Of Memory) since the native Handler is directly used is effectively avoided, and the collapse rate and the OOM problem of APP can be lowered.

Description

Technical field [0001] The embodiments of the present invention relate to computer technology, and in particular to a method and device for a function class to use Handler to process messages. Background technique [0002] The message handler (Handler) is a common application programming interface (API) used by Android developers for message transmission. It is mainly used for asynchronous message processing. After a message is sent, it first enters a message queue , The function that sends the message returns immediately, and the other part takes out the messages one by one in the message queue, and then processes the messages. However, with the improper use or carelessness of developers, it is easy to cause memory leaks. In severe cases, several MB of memory space will be occupied, thereby increasing the probability of occurrence of out of memory (OOM) and applications (Application , APP) crash probability. [0003] In order to avoid memory leaks caused by the use of Handler, y...

AI Technical Summary

Problems solved by technology

[0004] However, the above-mentioned implementation method of using static inner class plus WeakReference is too complicated. It is necessary to declare a static inner class in every place where Handler is used. If multiple Handlers are needed for message transmission, multiple Handlers need to be declared, and then instantiated one by one. And it is judged empty before each use, losing the simplicity of the original Handler

Images