CN115269252A - Application program fault processing method, device, equipment and storage medium - Google Patents
Application program fault processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115269252A CN115269252A CN202210938380.8A CN202210938380A CN115269252A CN 115269252 A CN115269252 A CN 115269252A CN 202210938380 A CN202210938380 A CN 202210938380A CN 115269252 A CN115269252 A CN 115269252A
- Authority
- CN
- China
- Prior art keywords
- target
- crash
- application program
- module
- interface
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
Abstract
The application relates to the technical field of artificial intelligence, and discloses an application program fault processing method, device, equipment and storage medium, wherein the method comprises the following steps: when a target interface loading instruction of a target application program is received, judging whether the target application program is triggered to crash by loading the target interface; when the target application program is triggered to crash when the target interface is loaded, judging whether a repair code for solving the problem of the crash of the target application program exists or not; when the repair code does not exist, identifying a target module which triggers the crash of the target application program, wherein the target module is one of view modules forming a target interface; the target module is not loaded when the target interface is loaded.
Description
Technical Field
The present application relates to the field of artificial intelligence technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing application program failures.
Background
At present, for many application programs, a program crash phenomenon inevitably occurs, and no matter how perfect a developer writes the program, the program crash cannot be completely avoided, and when the application program is abnormal, the self-processing mode is to flash back or stop running the application program, which affects user experience.
Disclosure of Invention
The application mainly aims to provide an application program fault processing method, device, equipment and storage medium, and aims to solve the problem that in the prior art, user experience is poor due to application program breakdown.
In a first aspect, the present application provides an application failure handling method, including:
when a target interface loading instruction of a target application program is received, judging whether loading the target interface triggers the target application program to crash or not;
when the target application program is triggered to crash when the target interface is loaded, judging whether a repair code for solving the problem of the crash of the target application program exists or not;
when the repair code does not exist, identifying a target module which triggers the crash of the target application program, wherein the target module is one of view modules forming the target interface;
the target module is not loaded when the target interface is loaded.
In a second aspect, the present application further provides an application failure processing apparatus, where the application failure processing apparatus includes:
the loading instruction receiving module is used for judging whether loading the target interface triggers the crash of the target application program or not when receiving a target interface loading instruction of the target application program;
the repair code query module is used for judging whether a repair code for solving the problem of the target application program breakdown exists or not when the target application program breakdown is triggered by loading the target interface;
the identification module is used for identifying a target module which triggers the crash of the target application program when the repair code does not exist, wherein the target module is one of view modules forming the target interface;
and the first loading module is used for not loading the target module when the target interface is loaded.
In a third aspect, the present application also provides a computer device, which includes a processor, a memory, and a computer program stored on the memory and executable by the processor, wherein the computer program, when executed by the processor, implements the steps of the application fault handling method as described above.
In a fourth aspect, the present application further provides a storage medium having a computer program stored thereon, where the computer program is executed by a processor to implement the steps of the application fault handling method as described above.
The application provides an application program fault processing method, device, equipment and storage medium, wherein when a target interface loading instruction of a target application program is received, whether the target application program is crashed is judged by loading the target interface; when the target application program is triggered to crash by loading the target interface, judging whether a repair code for solving the problem of the crash of the target application program exists or not; when the repair code does not exist, the target module triggering the target application program to crash is identified, and the target module is not loaded when the target interface is loaded, so that the problem that the target application program crashes due to the loading of the target interface can be avoided. Through the technical scheme provided by the application, the problem that the user experience is poor due to collapse of the application program in the prior art is solved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart illustrating steps of a method for processing an application failure according to an embodiment of the present application;
fig. 2 is a schematic block diagram of an application failure processing apparatus according to an embodiment of the present application;
fig. 3 is a schematic block diagram of a structure of a computer device according to an embodiment of the present application.
The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The flow diagrams depicted in the figures are merely illustrative and do not necessarily include all of the elements and operations/steps, nor do they necessarily have to be performed in the order depicted. For example, some operations/steps may be decomposed, combined or partially combined, so that the actual execution order may be changed according to the actual situation. In addition, although the division of the functional blocks is made in the device diagram, in some cases, it may be divided in blocks different from those in the device diagram.
The embodiment of the application provides an application program fault processing method, device, equipment and storage medium. The method is applied to terminal equipment, and the terminal equipment can be electronic equipment such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant and wearable equipment.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments and features of the embodiments described below can be combined with each other without conflict.
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a step of a method for processing an application program failure according to an embodiment of the present disclosure.
As shown in fig. 1, the application failure processing method includes steps S10 to S13.
Step S10, when a target interface loading instruction of a target application program is received, judging whether loading the target interface can trigger the target application program to crash.
It can be understood that the target application is a program currently running on the terminal device, and the target interface loading instruction is an instruction received by the terminal device to load a target interface in the target application.
For example, assuming that a target application on a terminal device is currently showing an order list interface, when a user clicks an "order details" button of an order on the order list interface, the terminal device receives an order details interface loading instruction of the target application, and triggers the target application to jump and load the order details interface.
It can be understood that the target application program is operated according to the code written by the developer, and if the code written by the developer is not strict enough and has a bug, when the terminal device receives the target interface loading instruction and loads the target interface in the target application program, the target application program may crash due to the situations of array boundary crossing, calling function error or memory leak.
Before the target interface is loaded, whether the target application program is crashed when the target interface is loaded is judged, the target interface is loaded after the judgment result is processed, and therefore the influence on user experience caused by program crash when the target application program is loaded can be avoided.
In some embodiments, the determining whether loading the target interface triggers the target application to crash includes:
acquiring program identification information of the target application program, and acquiring historical crash information matched with the program identification information;
acquiring interface identification information corresponding to the target interface, and inquiring whether a target crash log matched with the interface identification information exists according to the historical crash information;
and when the target crash log exists, judging whether loading the target interface triggers the target application program to crash or not according to the target crash log.
The program identification information is an application ID for identifying the identity of the target application program, and the interface identification information is an interface ID for identifying the identity of the target interface in the target application program.
It can be understood that the historical crash information matched according to the program identification information is crash log information recorded when a crash problem occurs in the process that the target application program runs on any terminal device.
Specifically, when the application program on any terminal device has a crash problem during the running process, crash log information is generated and uploaded to the server, so that the server establishes a mapping relationship with the crash log information according to the application ID of the crashed application program and stores the mapping relationship. Therefore, after the terminal device obtains the program identification information of the target application program, whether the historical crash information corresponding to the program identification information exists or not can be inquired through the server.
For example, assume that the program identification information and crash log information recorded in the server are as shown in the following table.
Watch I,
Assuming that the program identification information of the target application program is "application 1", the history crash information matching the program identification information acquired by the server includes "log 1", "log 2", and "log 3".
It is understood that the number of crash logs recorded in the historical crash information is uncertain, and each crash log records a crash interface ID when the target application crashes, and other crash information about the target application crashing.
Therefore, after the interface identification information and the historical crash information are obtained, whether a target crash log with the crash interface ID matched with the interface identification information exists in the historical crash information can be judged.
Illustratively, assume that the information recorded by the crash log in the historical crash information is as shown in Table two below.
A second meter,
| Crash log | Crash interface ID |
| Log 1 | HomePageVC |
| Log 2 | OrderListVC |
| Log 3 | OrderDetailVC |
Assuming that the interface identification information is "OrderDetailVC," there is a target crash log in the historical crash information that matches the interface identification information, and the determined target crash log is "log 3".
After the target crash log is obtained, whether the target application program is triggered to crash by loading the target interface can be judged according to the crash reason of the target crash log.
In some embodiments, the determining whether loading the target interface triggers the target application crash according to the target crash log includes:
acquiring the version number of the currently running target application program as a first version number, and acquiring the version number of the target application program with crash from the target crash log as a second version number;
and when the first version number is equal to the second version number, judging that the target application program is crashed when the target interface is loaded.
It can be understood that after the developer completes the iterative requirement of the product manager, a new version of the application program is released to the application market, and the version of the application program is distinguished by the version number.
The target crash log records a version number of the previously crashed target application program, that is, a second version number, and the version number of the currently running target application program of the terminal device is the first version number.
It will be appreciated that if the first version number is equal to the second version number. At this time, if the terminal device directly loads the target interface, there is a high possibility that the target application program may be crashed again. Thus, determining to load the target interface triggers the target application to crash.
And S11, when the target application program is triggered to crash by loading the target interface, judging whether a repair code for solving the problem of the crash of the target application program exists or not.
It will be appreciated that the target application crashes when the target interface is loaded, most likely due to problems with the running code of the target application being written. In addition, in the iterative development process of the target application program, the problem that the target application program crashes when the target interface is loaded may be solved by the developer, and at this time, if the developer uploads the code to a preset code warehouse, the terminal device can acquire the repair code from the code warehouse.
The repair code is used for solving the problem that the loading of the target interface causes the target application program to crash, so that when the target interface is judged to be loaded and the target application program is triggered to crash, whether the repair code exists or not can be judged firstly.
In some embodiments, the determining whether there is repair code to address the target application crash issue includes:
acquiring a crash coping strategy matched with the program identification information, and judging whether a target repairing strategy matched with the target crash log exists or not according to the crash coping strategy;
when the target repair policy exists, determining that a repair code for solving the crash problem of the target application exists.
It will be appreciated that there are many situations in which the target application may trigger a crash, for example, when interface 1 is loaded, and when interface 2 is loaded. After finding the crash problem according to the crash log, a developer tries to solve the crash problem, and stores a solution of the solved crash problem in the server to form a crash coping strategy.
However, the crash coping policy does not necessarily describe the repair policies of all the crash scenarios of the target application, and if the crash coping policy records the target repair policy matched with the target crash log, it indicates that the developer has solved the crash problem of the target application loading target interface, and therefore, determines that there is a repair code for solving the program crash problem
And S12, when the repair code does not exist, identifying a target module triggering the target application program to crash, wherein the target module is one of view modules forming the target interface.
In some embodiments, when there is no target repair policy in the crash coping policy that matches the target crash log, it is said that there is no repair code.
It will be appreciated that the target interface may include multiple view modules, and the target application loads the target interface by loading these view modules. And the situation that the target application program crashes when loading the target interface can occur in the process of loading some view modules in the target application program. And identifying the view module which causes the target application program to crash when the target interface is loaded from the view modules forming the target interface, namely obtaining the target module.
In some embodiments, said identifying a target module that triggered said target application crash comprises:
and identifying a target module which triggers the target application program to crash according to the target crash log.
It can be understood that the target crash log records a target view module ID that causes the target application program to crash when the target interface is loaded, and the target module can be determined according to the target view module ID.
Illustratively, assume that the target interface includes view modules as shown in Table three below.
A third table,
| View module | Module ID |
| Navigation bar view | NavigationBar |
| Commodity information view | CommodityMsgView |
| Order information view | OrderMsgView |
| Toolbar view | ToolBarView |
Assuming that the target view module ID causing the target application to crash when the target interface is loaded, which is recorded in the target crash log, is "ToolBarView", the "toolbar view" is determined to be the target module.
And S13, not loading the target module when loading the target interface.
It will be appreciated that in the absence of repair code, when the target interface is loaded, if the target module causing the target application crash continues to be loaded, the target application crash may be triggered again. Conversely, if the target module is not loaded, the target application will not crash when the target interface is loaded, at least because the target module is loaded.
In some embodiments, not loading the target module includes, but is not limited to, not calling initialization code of the target module.
For example, assuming that the view modules included in the target interface include a "navigation bar view", a "commodity information view", an "order information view", and a "toolbar view", assuming that the target module is a "toolbar view", the view modules currently displayed by the target interface after the target module is not loaded include a "navigation bar view", a "commodity information view", and an "order information view".
In some embodiments, after said not loading said target module while loading said target interface, said method further comprises:
acquiring a correlation module correlated with the target module, and monitoring whether the correlation module sends a message to the target module;
and when the association module is monitored to send a message to the target module, intercepting the message and triggering a module to disable reminding.
It can be understood that there may be an association relationship between view modules in the target interface, and a view module in the target interface that has an association relationship with the target module is an association module of the target module. After hiding the target module, there are still situations where the association module sends a message to the target module.
After the target module is not loaded, if the association module sends a message to the target module, the target interface may be triggered to load the target module again, which may cause the target application to crash, or after the association module sends a message to the target module, the target application may crash because the pointer of the target module, which is a recipient of the message, is empty.
For example, assuming that the target interface includes an "a view module" and a "B view module," when the target interface is loaded, detecting that the loading of the "B view module" causes the target application to crash, and detecting that no repair code can be pulled for solving the problem of the target application crashing, at this time, the target application does not load the "B view module" when the target interface is loaded. However, during the process of using the target application program by the terminal device, the user may click some buttons in the "a view module", and after clicking the buttons, the user sends a message to the "B view module" which is not loaded currently. At this point, if no message interception is done, it may trigger the target application to load the "B-view module" again, and cause the target application to crash.
In some implementations, the module disable alert can be a pop-up prompt box in the target interface to prompt the user that the target module has been disabled. In some embodiments, the reminding content in the prompt box may be a reminding message such as "module function is not on line", and of course, the reminding content in the prompt box may also be other content, which is not limited herein.
In the embodiment, after the association module is identified, the message sent by the association module to the target module is intercepted, so that the target application program can be prevented from being crashed, the forbidden reminding of the trigger module can tell the user that the target module is unavailable at present, and the user experience can be improved.
In some embodiments, after determining whether there is repair code to resolve the crash issue for the target application, the method further comprises:
when the repair code exists, pulling the repair code, and performing hot update operation on the target application program according to the repair code;
and loading the target interface.
It can be understood that by performing a hot update operation on the target application program, the code that would otherwise cause a program crash in the target application program may be replaced with the repair code. And after the target application program completes the hot updating operation, the target interface is loaded, so that the problem that the target application program for loading the target interface is crashed can be avoided.
In some embodiments, the pulling the repair code and performing a hot update operation on the target application according to the repair code includes:
and acquiring a warehouse address for storing the repair code from the target repair strategy, and pulling the repair code according to the warehouse address so as to perform hot update operation on the target application program according to the repair code.
It can be understood that the target repair policy further records a warehouse address for storing the repair code, and after the warehouse address is determined, the repair code can be pulled through the warehouse address to perform a hot update operation on the target application program.
In some embodiments, after the loading the target interface, the method further comprises:
monitoring the running condition of the target application program;
when the situation that the target application program is crashed is monitored, collecting crash information to generate a crash log;
and storing the crash log and updating the historical crash information according to the crash log.
It is understood that after the target interface is loaded, the target application may crash the target interface for other uncertain reasons, or when the target application subsequently exits the target interface and loads other interfaces, the target application may crash.
In this embodiment, when the target application program subsequently crashes, a crash log is generated and sent to the server for storage, and the server can update the historical crash information according to the received crash log. In the process of running the target application program, any subsequent terminal device can judge whether the interface to be loaded has a crash risk according to the updated historical crash information, and when judging that the crash risk exists, corresponding processing can be performed.
In some embodiments, after obtaining the crash coping policy matching the program identification information, the method further comprises:
storing the historical crash information and the crash coping strategy;
when a second interface loading instruction of the target application program is received, judging whether loading the second interface triggers the target application program to crash or not according to the historical crash information;
and when the second interface is loaded to trigger the target application program to crash, loading the second interface according to the crash coping strategy.
It is to be appreciated that the second interface can be any interface of the target application. And caching the historical collapse information and the collapse coping strategy into the memory, and when the subsequent terminal equipment receives a loading instruction of loading the second interface by the target application program, directly extracting the historical collapse information and the collapse coping strategy from the cache, and loading the second interface by using the historical collapse information and the collapse coping strategy so as to reduce the risk of the target application program being crashed when the second interface is loaded.
In this embodiment, when the target application program subsequently loads the second interface, it is not necessary to obtain the historical crash information and the crash coping policy from the server again, and the processing efficiency of the target application program for processing the crash abnormal condition can be improved.
In the application, when a target interface loading instruction of a target application program is received, whether the target application program is crashed is judged by loading the target interface; when the target application program is triggered to crash by loading the target interface, judging whether a repair code for solving the problem of the crash of the target application program exists or not; when the repair code does not exist, the target module triggering the target application program to crash is identified, and the target module is not loaded when the target interface is loaded, so that the problem that the target application program crashes due to the fact that the target interface is loaded can be solved. Through the technical scheme provided by the application, the problem that the user experience is poor due to collapse of the application program in the prior art is solved.
Referring to fig. 2, fig. 2 is a schematic block diagram of an application failure processing apparatus according to an embodiment of the present disclosure.
As shown in fig. 2, the application failure processing apparatus 201 includes:
a load instruction receiving module 2011, configured to, when a target interface load instruction of a target application is received, determine whether loading the target interface triggers crash of the target application;
a repair code query module 2012, configured to determine whether a repair code for solving the problem of the target application crash exists when the target application crash is triggered by loading the target interface;
an identifying module 2013, configured to identify, when the repair code does not exist, a target module that triggers a crash of the target application, where the target module is one of view modules that form the target interface;
a first loading module 2014, configured to not load the target module when the target interface is loaded.
In some embodiments, the apparatus 201 for processing an application program failure further includes a second loading module 2015, after the repair code query module 2012 determines whether there is a repair code to solve the problem of the target application program crash, where the second loading module 2015 is configured to, when there is the repair code, pull the repair code and perform a hot update operation on the target application program according to the repair code;
and loading the target interface.
In some embodiments, the load instruction receiving module 2011, when determining whether loading the target interface would trigger the target application crash, includes:
acquiring program identification information of the target application program, and acquiring historical crash information matched with the program identification information;
acquiring interface identification information corresponding to the target interface, and inquiring whether a target crash log matched with the interface identification information exists according to the historical crash information;
and when the target crash log exists, judging whether loading the target interface triggers the target application program to crash or not according to the target crash log.
In some embodiments, the load instruction receiving module 2011, when determining whether loading the target interface would trigger the target application to crash according to the target crash log, includes:
acquiring the version number of the currently running target application program as a first version number, and acquiring the version number of the target application program with crash from the target crash log as a second version number;
and when the first version number is equal to the second version number, judging that the target application program is crashed when the target interface is loaded.
In some embodiments, the repair code query module 2012, when determining whether there is repair code that solves the target application crash problem, includes:
acquiring a crash coping strategy matched with the program identification information, and judging whether a target repairing strategy matched with the target crash log exists or not according to the crash coping strategy;
when the target repair strategy exists, judging that a repair code for solving the crash problem of the target application program exists;
when the second loading module 2015 pulls the repair code and performs a hot update operation on the target application program according to the repair code, the second loading module 2015 includes:
and acquiring a warehouse address for storing the repair code from the target repair strategy, and pulling the repair code according to the warehouse address so as to perform hot update operation on the target application program according to the repair code.
In some embodiments, the identifying module 2013, in identifying a target module that triggers the target application crash, comprises:
and identifying a target module which triggers the target application program to crash according to the target crash log.
In some embodiments, the application fault handling apparatus 201 further includes a message interception module 2016, where after the first loading module 2014 does not load the target module when the target interface is loaded, the message interception module 2016 is configured to obtain an association module associated with the target module, and monitor whether the association module sends a message to the target module;
and when the association module is monitored to send a message to the target module, intercepting the message and triggering a module to disable reminding.
It should be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the apparatus and each module and unit described above may refer to the corresponding processes in the foregoing embodiment of the method for processing the application program fault, and are not described herein again.
The apparatus provided by the above embodiments may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 3.
Referring to fig. 3, fig. 3 is a schematic block diagram of a structure of a computer device according to an embodiment of the present disclosure. The computer device includes, but is not limited to, a terminal device.
As shown in fig. 3, the computer device 301 includes a processor 3011, a memory and a network interface, which are connected through a system bus, where the memory may include a storage medium 3012 and an internal storage 3015, and the storage medium 3012 may be non-volatile or volatile.
The storage medium 3012 may store an operating system and computer programs. The computer program includes program instructions that, when executed, cause the processor 3011 to perform any of the application fault handling methods.
The internal memory 3015 provides an environment for running a computer program in the storage medium 3012, and when the computer program is executed by the processor 3011, the computer program may cause the processor 3011 to execute any one of the application failure processing methods.
The network interface is used for network communication, such as sending assigned tasks and the like. Those skilled in the art will appreciate that the architecture shown in fig. 3 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
It should be understood that Processor 3011 may be a Central Processing Unit (CPU), and that Processor 3011 may also be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In some embodiments, the processor 3011 is configured to run a computer program stored in the memory to implement the following steps:
when a target interface loading instruction of a target application program is received, judging whether loading the target interface triggers the target application program to crash or not;
when the target application program is triggered to crash by loading the target interface, judging whether a repair code for solving the problem of the crash of the target application program exists or not;
when the repair code does not exist, identifying a target module which triggers the target application program to crash, wherein the target module is one of view modules forming the target interface;
the target module is not loaded when the target interface is loaded.
In some embodiments, the processor 3011, after determining whether there is repair code to resolve the crash issue for the target application, is further configured to:
when the repair code exists, pulling the repair code, and performing hot update operation on the target application program according to the repair code;
and loading the target interface.
In some embodiments, the processor 3011, when determining whether loading the target interface would trigger the target application to crash, is configured to:
acquiring program identification information of the target application program, and acquiring historical crash information matched with the program identification information;
acquiring interface identification information corresponding to the target interface, and inquiring whether a target crash log matched with the interface identification information exists according to the historical crash information;
and when the target crash log exists, judging whether loading the target interface triggers the target application program to crash or not according to the target crash log.
In some embodiments, when determining, according to the target crash log, whether loading the target interface would trigger the target application crash, the processor 3011 is configured to implement:
acquiring the version number of the currently running target application program as a first version number, and acquiring the version number of the target application program with crash from the target crash log as a second version number;
and when the first version number is equal to the second version number, judging that the target application program is triggered to crash by loading the target interface.
In some embodiments, the processor 3011, when determining whether there is repair code to resolve the crash issue for the target application, is configured to:
acquiring a crash coping strategy matched with the program identification information, and judging whether a target repairing strategy matched with the target crash log exists or not according to the crash coping strategy;
when the target repair strategy exists, judging that a repair code for solving the crash problem of the target application program exists;
when the processor 3011 pulls the repair code and performs a hot update operation on the target application according to the repair code, it is configured to:
and acquiring a warehouse address for storing the repair code from the target repair strategy, and pulling the repair code according to the warehouse address so as to perform hot update operation on the target application program according to the repair code.
In some embodiments, the processor 3011, when identifying a target module that triggers the target application crash, is configured to:
and identifying a target module which triggers the target application program to crash according to the target crash log.
In some embodiments, after the processor 3011 does not load the target module when loading the target interface, it is further configured to:
acquiring a correlation module correlated with the target module, and monitoring whether the correlation module sends a message to the target module;
and when the association module is monitored to send a message to the target module, intercepting the message and triggering a module to disable reminding.
It should be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the computer device described above may refer to the corresponding process in the foregoing embodiment of the method for processing a failure of an application, and details are not described here again.
The present application also provides a storage medium, which is a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, where the computer program includes program instructions, and a method implemented when the program instructions are executed may refer to various embodiments of the application fault handling method in the present application.
The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiment, for example, a hard disk or a memory of the computer device. The computer readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the computer device.
It is to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification 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 in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items and includes such combinations. It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or system comprising the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments. The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of various equivalent modifications or substitutions within the technical scope of the present application, and these modifications or substitutions should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. An application program fault processing method is applied to terminal equipment, and is characterized by comprising the following steps:
when a target interface loading instruction of a target application program is received, judging whether loading the target interface triggers the target application program to crash or not;
when the target application program is triggered to crash by loading the target interface, judging whether a repair code for solving the problem of the crash of the target application program exists or not;
when the repair code does not exist, identifying a target module which triggers the crash of the target application program, wherein the target module is one of view modules forming the target interface;
the target module is not loaded when the target interface is loaded.
2. The method of claim 1, wherein after determining whether there is repair code to resolve the target application crash issue, the method further comprises:
when the repair code exists, pulling the repair code, and performing hot update operation on the target application program according to the repair code;
and loading the target interface.
3. The method of claim 2, wherein determining whether loading the target interface triggers the target application to crash comprises:
acquiring program identification information of the target application program, and acquiring historical crash information matched with the program identification information;
acquiring interface identification information corresponding to the target interface, and inquiring whether a target crash log matched with the interface identification information exists according to the historical crash information;
and when the target crash log exists, judging whether loading the target interface triggers the target application program to crash or not according to the target crash log.
4. The method of claim 3, wherein determining whether loading the target interface triggers the target application to crash based on the target crash log comprises:
acquiring the version number of the currently running target application program as a first version number, and acquiring the version number of the target application program which crashes from the target crash log as a second version number;
and when the first version number is equal to the second version number, judging that the target application program is triggered to crash by loading the target interface.
5. The method of claim 3, wherein determining whether repair code exists to address the crash issue for the target application comprises:
acquiring a crash coping strategy matched with the program identification information, and judging whether a target repairing strategy matched with the target crash log exists or not according to the crash coping strategy;
when the target repair strategy exists, judging that a repair code for solving the crash problem of the target application program exists;
the pulling the repair code and performing hot update operation on the target application program according to the repair code comprises the following steps:
and acquiring a warehouse address for storing the repair code from the target repair strategy, and pulling the repair code according to the warehouse address so as to perform hot update operation on the target application program according to the repair code.
6. The method of claim 3, wherein identifying a target module that triggers the target application to crash comprises:
and identifying a target module which triggers the target application program to crash according to the target crash log.
7. The method of any of claims 1-5, wherein after the target module is not loaded while the target interface is loaded, the method further comprises:
acquiring a correlation module correlated with the target module, and monitoring whether the correlation module sends a message to the target module;
and when the association module is monitored to send a message to the target module, intercepting the message and triggering a module to disable reminding.
8. An apparatus for processing an application crash problem, comprising:
the loading instruction receiving module is used for judging whether loading the target interface triggers the crash of the target application program or not when receiving a target interface loading instruction of the target application program;
the repair code query module is used for judging whether a repair code for solving the problem of the target application program breakdown exists or not when the target application program breakdown is triggered by loading the target interface;
the identification module is used for identifying a target module which triggers the crash of the target application program when the repair code does not exist, wherein the target module is one of view modules forming the target interface;
and the first loading module is used for not loading the target module when the target interface is loaded.
9. A computer arrangement comprising a processor, a memory, and a computer program stored on the memory and executable by the processor, wherein the computer program, when executed by the processor, implements the steps of the application fault handling method according to any one of claims 1 to 7.
10. A computer-readable storage medium, having a computer program stored thereon, wherein the computer program, when being executed by a processor, carries out the steps of the application fault handling method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210938380.8A CN115269252A (en) | 2022-08-05 | 2022-08-05 | Application program fault processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210938380.8A CN115269252A (en) | 2022-08-05 | 2022-08-05 | Application program fault processing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115269252A true CN115269252A (en) | 2022-11-01 |
Family
ID=83749468
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210938380.8A Pending CN115269252A (en) | 2022-08-05 | 2022-08-05 | Application program fault processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115269252A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116679900A (en) * | 2022-12-23 | 2023-09-01 | 荣耀终端有限公司 | Audio service processing method, firmware loading method and related devices |
-
2022
- 2022-08-05 CN CN202210938380.8A patent/CN115269252A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116679900A (en) * | 2022-12-23 | 2023-09-01 | 荣耀终端有限公司 | Audio service processing method, firmware loading method and related devices |
| CN116679900B (en) * | 2022-12-23 | 2024-04-09 | 荣耀终端有限公司 | Audio service processing method, firmware loading method and related devices |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109284217B (en) | Application program exception handling method and device, electronic equipment and storage medium | |
| CN108848142B (en) | Message pushing method and device, computer equipment and storage medium | |
| WO2019148727A1 (en) | Electronic device, redis-based exception warning method and storage medium | |
| CN112035472B (en) | Data processing method, device, computer equipment and storage medium | |
| CN110618890B (en) | Fault processing method and device, electronic equipment and computer readable storage medium | |
| WO2019140739A1 (en) | Method for determining return visits to client, and electronic apparatus and computer-readable storage medium | |
| CN110866258A (en) | Method for quickly positioning bug, electronic device and storage medium | |
| CN109634802B (en) | Process monitoring method and terminal equipment | |
| CN116244138A (en) | Method and device for identifying abnormal operation of application, electronic equipment and storage medium | |
| CN115269252A (en) | Application program fault processing method, device, equipment and storage medium | |
| US20070294584A1 (en) | Detection and isolation of data items causing computer process crashes | |
| CN111522706A (en) | Method and device for monitoring page abnormity of front-end application | |
| EP2860633A1 (en) | Method for maintaining file system of computer system | |
| CN110881224A (en) | Network long connection method, device, equipment and storage medium | |
| CN109408265B (en) | IOS abnormal operation protection method and device, terminal equipment and storage medium | |
| US20080216057A1 (en) | Recording medium storing monitoring program, monitoring method, and monitoring system | |
| CN113467981A (en) | Exception handling method and device | |
| US20210382764A1 (en) | Comparisons of application programming interface interactions to determine compatibilities | |
| CN111400085A (en) | Transaction rollback exception processing method and device, computer equipment and storage medium | |
| CN113778763B (en) | Intelligent switching method and system for three-way interface service faults | |
| CN110309647B (en) | Processing method and device for application program, electronic equipment and storage medium | |
| US11671440B1 (en) | Detection failure monitoring system | |
| CN105511848B (en) | Detection method and device for dynamic link library | |
| CN107797800B (en) | Data processing method for multiple associated service systems, electronic device and medium | |
| CN111708783A (en) | Data storage and data recovery method and device and electronic equipment |
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 |