CN115269252A - Application fault handling method, device, device and storage medium - Google Patents

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

Application program fault handling method, device, equipment and storage medium

technical field

The present application relates to the technical field of artificial intelligence, and in particular to a method, device, device and storage medium for handling application faults.

Background technique

At present, for many applications, it is inevitable that program crashes will occur. No matter how perfect the developer writes the program, the occurrence of program crashes cannot be completely avoided. When an exception occurs, the application will handle it by itself. To crash or stop running the application, affecting user experience.

Contents of the invention

The main purpose of the present application is to provide a method, device, device, and storage medium for handling application failures, aiming at solving the problem in the prior art that application failures lead to poor user experience.

In a first aspect, the present application provides a method for handling application faults, including:

When a target interface loading instruction of the target application is received, it is determined whether loading the target interface will trigger the target application to crash;

When loading the target interface will trigger the target application program to crash, determine whether there is a repair code to solve the target application program crash problem;

When the repair code does not exist, identifying a target module that triggers the crash of the target application program, wherein the target module is one of the view modules constituting the target interface;

The target module is not loaded when the target interface is loaded.

In a second aspect, the present application also provides an application program fault processing device, the application program fault processing device comprising:

A loading instruction receiving module, configured to determine whether loading the target interface will trigger the target application to crash when receiving the target interface loading instruction of the target application;

A repair code query module, used to determine whether there is a repair code to solve the crash problem of the target application when loading the target interface will trigger the crash of the target application;

An identification module, configured to identify a target module that triggers the crash of the target application program when the repair code does not exist, wherein the target module is one of the view modules constituting the target interface;

The first loading module is configured not to load the target module when loading the target interface.

In a third aspect, the present application further provides a computer device, the computer device includes a processor, a memory, and a computer program stored on the memory and executable by the processor, wherein the computer program is executed by the When the processor executes, it implements the steps of the above-mentioned application program fault handling method.

In a fourth aspect, the present application further provides a storage medium, where a computer program is stored on the computer-readable storage medium, wherein when the computer program is executed by a processor, the steps of the above-mentioned application program fault handling method are realized.

The present application provides a method, device, device, and storage medium for handling application faults. In the present application, when a target interface loading instruction of the target application is received, it is judged whether loading the target interface will trigger the target application to crash; when loading the target When the interface triggers the crash of the target application, determine whether there is a repair code to solve the crash of the target application; when there is no repair code, identify the target module that triggers the crash of the target application, and do not load the target module when loading the target interface, that is The problem that the target application crashes due to loading the target interface can be avoided. Through the technical solution provided by the present application, the problem in the prior art that the crash of the application program leads to poor user experience is solved.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present application more clearly, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present application. Ordinary technicians can also obtain other drawings based on these drawings on the premise of not paying creative work.

FIG. 1 is a schematic flowchart of the steps of a method for handling application faults provided in an embodiment of the present application;

FIG. 2 is a schematic block diagram of an application program fault processing device provided by an embodiment of the present application;

FIG. 3 is a schematic structural block diagram of a computer device provided by an embodiment of the present application.

The realization, functional features and advantages of the present application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of them. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.

The flow charts shown in the drawings are just illustrations, and do not necessarily include all contents and operations/steps, nor must they be performed in the order described. For example, some operations/steps can be decomposed, combined or partly combined, so the actual order of execution may be changed according to the actual situation. In addition, although the functional modules are divided in the schematic diagram of the device, in some cases, they may be divided into modules different from those in the schematic diagram of the device.

Embodiments of the present application provide a method, device, device, and storage medium for handling application faults. Wherein, the method is applied to a terminal device, and the terminal device may be an electronic device such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, and a wearable device.

Some implementations of the present application will be described in detail below in conjunction with the accompanying drawings. In the case of no conflict, the following embodiments and features in the embodiments can be combined with each other.

Please refer to FIG. 1 . FIG. 1 is a schematic flowchart of steps of a method for handling an application program failure provided by an embodiment of the present application.

As shown in FIG. 1 , the application program fault handling method includes steps S10 to S13.

Step S10, when receiving a target interface loading instruction of the target application, determine whether loading the target interface will trigger the target application to crash.

It can be understood that the target application program 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 the target interface in the target application program.

Exemplarily, assuming that the target application on the terminal device is currently displaying an order list interface, when the user clicks the "order details" button of an order on the order list interface, the terminal device receives the order of the target application The command to load the details interface triggers the target application to jump and load the order details interface.

It can be understood that the target application program runs according to the code written by the developer. If the code written by the developer is not rigorous enough and there are loopholes, when the terminal device receives the target interface loading instruction and the target application program loads the target interface, there may be The target application crashes due to conditions such as an array out of bounds, an error in calling a function, or a memory leak.

Before loading the target interface, first judge whether loading the target interface will cause the target application to crash, and then load the target interface after processing according to the judgment result, which can prevent the target application from affecting the user experience due to the program crash when loading the target interface.

In some implementation manners, the judging whether loading the target interface will trigger the crash of the target application program includes:

Obtaining program identification information of the target application program, and acquiring historical crash information matching the program identification information;

Obtaining the interface identification information corresponding to the target interface, and querying whether there is a target crash log matching the interface identification information according to the historical crash information;

When the target crash log exists, it is judged according to the target crash log whether loading the target interface will trigger the target application program to crash.

Wherein, 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 the crash log information recorded when the target application program crashes on any terminal device.

Specifically, when an application program on any terminal device crashes during running, generate crash log information and upload the crash log information to the server, so that the server can establish a Map the relationship and save it. Therefore, after the terminal device obtains the program identification information of the target application program, it can query whether there is historical crash information corresponding to the program identification information through the server.

Exemplarily, it is assumed that the program identification information and crash log information recorded in the server are shown in Table 1 below.

Table I,

Assuming that the program identification information of the target application is "application 1", the historical crash information obtained by the server and matching the program identification information includes "log 1", "log 2" and "log 3".

It can be understood that the number of crash logs recorded in the historical crash information is uncertain, and each crash log records the crash interface ID when the target application crashes, and other crash information of the target application crash.

Therefore, after obtaining the interface identification information and historical crash information, it can be determined whether there is a target crash log whose crash interface ID matches the interface identification information in the historical crash information.

Exemplarily, it is assumed that the information recorded in the crash log in the historical crash information is shown in Table 2 below.

Table II,

crash log Crash UI ID log 1 HomePageVC log 2 OrderListVC log 3 OrderDetailVC

Assuming that the interface identification information is "OrderDetailVC", there is a target crash log matching the interface identification information in the historical crash information, and the determined target crash log is "log 3".

After the target crash log is obtained, it can be judged according to the crash cause of the target crash log whether loading the target interface will trigger the crash of the target application.

In some implementation manners, the judging according to the target crash log whether loading the target interface will trigger the target application to crash includes:

Obtaining the version number of the currently running target application program as a first version number, and obtaining the version number of the target application program that crashed from the target crash log as a second version number;

When the first version number is equal to the second version number, it is determined that loading the target interface will trigger the target application program to crash.

It can be understood that when the developer completes the iterative requirements of the product manager, he will release a new version of the application to the application market, and use the version number to distinguish the version of the application.

The target crash log records the version number of the target application program that crashed before, that is, the second version number, and the version number of the target application program currently running on the terminal device is the first version number.

It can be understood 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, it is very likely that the target application program will crash again. Therefore, it is determined that loading the target interface will trigger the target application to crash.

Step S11 , when loading the target interface will trigger the target application program to crash, determine whether there is a repair code to solve the problem of the target application program crashing.

It can be understood that the crash of the target application program when loading the target interface is most likely caused by a problem with the running code of the written target application program. In addition, during the iterative development of the target application, the developer may have solved the problem of the target application crashing when loading the target interface. At this time, if the developer uploads the code to the preset code warehouse, the terminal device can Get the fix code from the code repository.

The repair code is the code used to solve the problem that the target application program crashes due to loading the target interface. Therefore, when it is determined that loading the target interface will trigger the target application program to crash, you can first determine whether there is a repair code.

In some implementation manners, the judging whether there is a repair code for solving the crash problem of the target application includes:

Obtaining a crash response strategy that matches the program identification information, and judging whether there is a target repair strategy that matches the target crash log according to the crash response strategy;

When the target repair strategy exists, it is determined that there is a repair code for solving the crash problem of the target application program.

It can be understood that there may be multiple situations that trigger the crash of the target application program, for example, it may crash when the interface 1 is loaded, and it may also crash when the interface 2 is loaded. After the developer discovers the crash problem based on the crash log, he will try to solve the crash problem, and store the solution to the crash problem in the server to form a crash response strategy.

However, the crash response strategy does not necessarily record the repair strategy for all crash scenarios of the target application. If the crash response strategy records a target repair strategy that matches the target crash log, it means that the developer has solved the target application loading target. The crash problem of the interface, therefore, it is determined that there is a fix code to solve the program crash problem

Step S12. When the repair code does not exist, identify the target module that triggers the crash of the target application program, wherein the target module is one of the view modules constituting the target interface.

In some embodiments, when there is no target repair policy matching the target crash log in the crash response policy, it means that there is no repair code.

It can be understood that the target interface may contain multiple view modules, and the target application program loads the target interface by loading these view modules. However, when the target application program loads the target interface and crashes, it may occur during the process of loading some of the view modules. The view module that causes the target application program to crash when the target interface is loaded is identified from the view modules constituting the target interface, that is, the target module is obtained.

In some implementation manners, the identifying the target module that triggers the crash of the target application program includes:

A target module that triggers the crash of the target application program is identified according to the target crash log.

It can be understood that when the target interface is loaded, the target view module ID that causes the target application program to crash is recorded in the target crash log, and the target module can be determined according to the target view module ID.

Exemplarily, it is assumed that the view modules included in the target interface are shown in Table 3 below.

Table three,

view module module ID navigation bar view NavigationBar Product information view CommodityMsgView Order Information View OrderMsgView toolbar view ToolBarView

Assuming that the ID of the target view module that causes the target application to crash when loading the target interface recorded in the target crash log is "ToolBarView", then determine "ToolBarView" as the target module.

Step S13, the target module is not loaded when the target interface is loaded.

It can be understood that if the target module that causes the crash of the target application continues to be loaded when the target interface is loaded in the absence of the repair code, the crash of the target application may be triggered again. On the contrary, if the target module is not loaded, the target application will at least not crash due to loading the target module when loading the target interface.

In some implementations, not loading the target module includes but is not limited to not calling the initialization code of the target module.

Exemplarily, assume that the view modules included in the target interface include "navigation bar view", "commodity information view", "order information view" and "toolbar view", assuming that the target module is "toolbar view", then no After the target module is loaded, the view modules currently displayed on the target interface include "navigation bar view", "commodity information view" and "order information view".

In some implementation manners, after the target module is not loaded when the target interface is loaded, the method further includes:

Obtain an associated module associated with the target module, and monitor whether the associated module sends a message to the target module;

When the monitoring module sends a message to the target module, intercept the message and trigger the module to disable the reminder.

It can be understood that there may be an associated relationship between the view modules in the target interface, and the view modules in the target interface that are associated with the target module are the associated modules of the target module. After hiding the target module, there is still a situation where the associated module sends a message to the target module.

After the target module is not loaded, if the associated module sends a message to the target module, it may trigger the target interface to load the target module again and cause the target application to crash, or after the associated module sends a message to the target module, because as a message The receiver's target module pointer is null and the target application crashes.

Exemplarily, assuming that the target interface includes "A view module" and "B view module", when loading the target interface, it is detected that loading "B view module" will cause the target application to crash, and it is detected that no repair code can be pulled It is used to solve the problem that the target application crashes. At this time, the target application does not load the "B view module" when loading the target interface. However, during the process of using the target application program on the terminal device, the user may click some buttons in the "A view module", and after clicking these buttons, a message will be sent to the "B view module" that is not currently loaded. At this time, if the message interception is not performed, the target application may be triggered to load the "B view module" again, and cause the target application to crash.

In some implementations, the module disabling reminder may be popping up a prompt box in the target interface to remind the user that the target module has been disabled. In some implementations, the reminder content in the prompt box may be a reminder message such as "the module function is not online". Of course, the reminder content in the prompt box may also be other content, which is not limited here.

In this embodiment, after identifying the associated module, intercepting the message sent by the associated module to the target module can prevent the target application from crashing, and triggering the module to disable the reminder can tell the user that the target module is currently unavailable, which can improve user experience.

In some implementation manners, after determining whether there is a repair code for solving the crash problem of the target application program, the method further includes:

When the repair code exists, pull the repair code, and perform a hot update operation on the target application program according to the repair code;

Load the target interface.

It can be understood that by performing a hot update operation on the target application program, the code in the target application program that would otherwise cause a program crash can be replaced with the repair code. The target interface is loaded after the target application program completes the hot update operation, so that the problem of the target application program crashing when loading the target interface can be avoided.

In some implementation manners, the pulling the repair code, and performing a hot update operation on the target application program according to the repair code includes:

A warehouse address storing the repair code is obtained from the target repair policy, and the repair code is pulled according to the warehouse address, so as to perform a hot update operation on the target application program according to the repair code.

It can be understood that the address of the warehouse storing the repair code is also recorded in the target repair policy. 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.

In some implementation manners, after the loading of the target interface, the method further includes:

monitor the operation of the target application;

When the crash of the target application is detected, the crash information is collected to generate a crash log;

storing the crash log and updating the historical crash information according to the crash log.

It can be understood that after the target interface is loaded, the target application program may crash due to other uncertain reasons on the target interface, or, when the target application subsequently exits the target interface and loads other interfaces, it may also crash. There are instances where the target application crashes.

In this embodiment, when the target application subsequently crashes, a crash log is generated and sent to the server for storage, and the server can update 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 there is a crash risk in the interface to be loaded according to the updated historical crash information, and when it is determined that there is a crash risk, corresponding processing can be performed.

In some implementation manners, after the acquisition of the crash response strategy matching the program identification information, the method further includes:

storing the historical crash information and the crash response strategy;

When receiving the second interface loading instruction of the target application, judging according to the historical crash information whether loading the second interface will trigger the target application to crash;

When loading the second interface will trigger the target application program to crash, load the second interface according to the crash response strategy.

It can be understood that the second interface may be any interface of the target application program. Cache historical crash information and crash response strategies in the memory, then when the subsequent terminal device receives the loading instruction of the target application to load the second interface, it can directly extract historical crash information and crash response strategies from the cache, and use the historical crash The information and the crash response strategy are used to load the second interface, so as to reduce the risk that the loading of the second interface triggers the crash of the target application.

In this embodiment, when the target application program subsequently loads the second interface, there is no need to obtain historical crash information and crash handling strategies from the server again, which can improve the processing efficiency of the target application program in dealing with abnormal situations of crashes.

In this application, when receiving the target interface loading instruction of the target application, judge whether loading the target interface will trigger the target application to crash; when loading the target interface will trigger the target application to crash, judge whether there is a solution to the target application crash problem The repair code; when there is no repair code, identify the target module that triggers the crash of the target application, and not load the target module when loading the target interface, so as to avoid the problem that the target application crashes due to loading the target interface. Through the technical solution provided by the present application, the problem in the prior art that the crash of the application program leads to poor user experience is solved.

Please refer to FIG. 2 . FIG. 2 is a schematic block diagram of an application program fault handling device provided by an embodiment of the present application.

As shown in Figure 2, the application program failure processing device 201 includes:

The loading instruction receiving module 2011 is used to determine whether loading the target interface will trigger the target application to crash when receiving the target interface loading instruction of the target application;

The repair code query module 2012 is used to determine whether there is a repair code to solve the crash problem of the target application when loading the target interface will trigger the crash of the target application;

An identification module 2013, configured to identify the target module that triggers the crash of the target application program when the repair code does not exist, wherein the target module is one of the view modules constituting the target interface;

The first loading module 2014 is configured not to load the target module when loading the target interface.

In some implementations, the application program failure handling device 201 further includes a second loading module 2015, after the repair code query module 2012 judges whether there is a repair code that solves the crash problem of the target application program, the second The second loading module 2015 is used to pull the repair code when the repair code exists, and perform a hot update operation on the target application program according to the repair code;

Load the target interface.

In some implementations, when the loading instruction receiving module 2011 determines whether loading the target interface will trigger the target application to crash, it includes:

Obtaining program identification information of the target application program, and acquiring historical crash information matching the program identification information;

Obtaining the interface identification information corresponding to the target interface, and querying whether there is a target crash log matching the interface identification information according to the historical crash information;

When the target crash log exists, it is judged according to the target crash log whether loading the target interface will trigger the target application program to crash.

In some implementations, when the loading instruction receiving module 2011 determines whether loading the target interface will trigger the target application crash according to the target crash log, it includes:

Obtaining the version number of the currently running target application program as a first version number, and obtaining the version number of the target application program that crashed from the target crash log as a second version number;

When the first version number is equal to the second version number, it is determined that loading the target interface will trigger the target application program to crash.

In some implementation manners, when the repair code query module 2012 determines whether there is a repair code that solves the crash problem of the target application program, it includes:

Obtaining a crash response strategy that matches the program identification information, and judging whether there is a target repair strategy that matches the target crash log according to the crash response strategy;

When the target repair strategy exists, it is determined that there is a repair code to solve the crash problem of the target application;

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, it includes:

A warehouse address storing the repair code is obtained from the target repair policy, and the repair code is pulled according to the warehouse address, so as to perform a hot update operation on the target application program according to the repair code.

In some implementation manners, when the identification module 2013 identifies the target module that triggers the crash of the target application, it includes:

A target module that triggers the crash of the target application program is identified according to the target crash log.

In some implementations, the application program fault handling device 201 further includes a message interception module 2016, after the first loading module 2014 does not load the target module when loading the target interface, the message interception module 2016 It is used to obtain an associated module associated with the target module, and monitor whether the associated module sends a message to the target module;

When the monitoring module sends a message to the target module, intercept the message and trigger the module to disable the reminder.

It should be noted that those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described devices and modules and units can refer to the corresponding The process will not be repeated here.

The apparatus provided in the foregoing embodiments may be implemented in the form of a computer program, and the computer program may be run on a computer device as shown in FIG. 3 .

Please refer to FIG. 3 . FIG. 3 is a schematic structural block diagram of a computer device provided by an embodiment of the present application. The computer equipment includes but is not limited to terminal equipment.

As shown in FIG. 3 , the computer device 301 includes a processor 3011 connected through a system bus, a memory, and a network interface, wherein the memory may include a storage medium 3012 and an internal memory 3015, and the storage medium 3012 may be non-volatile, or is volatile.

The storage medium 3012 can store an operating system and computer programs. The computer program includes program instructions, and when the program instructions are executed, the processor 3011 can be executed to execute any application program fault handling method.

The processor 3011 is used to provide computing and control capabilities to support the operation of the entire computer device.

The internal memory 3015 provides an environment for the running of the computer program in the storage medium 3012. When the computer program is executed by the processor 3011, the processor 3011 can execute any application program fault handling method.

This network interface is used for network communication, such as sending assigned tasks, etc. Those skilled in the art can understand that the structure shown in Figure 3 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation to the computer equipment on which the solution of the application is applied. The specific computer equipment can be More or fewer components than shown in the figures may be included, or some components may be combined, or have a different arrangement of components.

It should be understood that the processor 3011 may be a central processing unit (Central Processing Unit, CPU), and the processor 3011 may also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Wherein, the general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Wherein, in some implementation manners, the processor 3011 is configured to run a computer program stored in a memory, so as to realize the following steps:

When a target interface loading instruction of the target application is received, it is determined whether loading the target interface will trigger the target application to crash;

When loading the target interface will trigger the target application program to crash, determine whether there is a repair code to solve the target application program crash problem;

When the repair code does not exist, identifying a target module that triggers the crash of the target application program, wherein the target module is one of the view modules constituting the target interface;

The target module is not loaded when the target interface is loaded.

In some implementation manners, after the processor 3011 determines whether there is a repair code for solving the crash problem of the target application program, it is further configured to:

When the repair code exists, pull the repair code, and perform a hot update operation on the target application program according to the repair code;

Load the target interface.

In some implementation manners, when the processor 3011 determines whether loading the target interface will trigger the crash of the target application, it is configured to:

Obtaining program identification information of the target application program, and acquiring historical crash information matching the program identification information;

Obtaining the interface identification information corresponding to the target interface, and querying whether there is a target crash log matching the interface identification information according to the historical crash information;

When the target crash log exists, it is judged according to the target crash log whether loading the target interface will trigger the target application program to crash.

In some implementations, when the processor 3011 judges according to the target crash log whether loading the target interface will trigger the target application to crash, it is configured to:

Obtaining the version number of the currently running target application program as a first version number, and obtaining the version number of the target application program that crashed from the target crash log as a second version number;

When the first version number is equal to the second version number, it is determined that loading the target interface will trigger the target application program to crash.

In some implementation manners, the processor 3011 is configured to implement:

Obtaining a crash response strategy that matches the program identification information, and judging whether there is a target repair strategy that matches the target crash log according to the crash response strategy;

When the target repair strategy exists, it is determined that there is a repair code to solve the crash problem of the target application;

When the processor 3011 pulls the repair code and performs a hot update operation on the target application program according to the repair code, it is used to implement:

A warehouse address storing the repair code is obtained from the target repair policy, and the repair code is pulled according to the warehouse address, so as to perform a hot update operation on the target application program according to the repair code.

In some implementation manners, when the processor 3011 identifies the target module that triggers the crash of the target application, it is configured to:

A target module that triggers the crash of the target application program is identified according to the target crash log.

In some implementation manners, after the processor 3011 does not load the target module when loading the target interface, it is further configured to:

Obtain an associated module associated with the target module, and monitor whether the associated module sends a message to the target module;

When the monitoring module sends a message to the target module, intercept the message and trigger the module to disable the reminder.

It should be noted that those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the computer device described above can refer to the corresponding process in the above-mentioned embodiment of the application program fault handling method, which is not described here. Let me repeat.

The embodiment of the present application also provides a storage medium, the storage medium is a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium, and the computer program includes program instructions, and when the program instructions are executed, For the implemented method, reference may be made to various embodiments of the application program fault handling method in this application.

Wherein, the computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as a hard disk or a memory of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard disk equipped on the computer device, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc.

It should be understood that the terms used in the specification of this application are for the purpose of describing specific embodiments only and are not intended to limit the application. As used in this specification and the appended claims, the singular forms "a", "an" and "the" are intended to include plural referents unless the context clearly dictates otherwise.

It should also be understood that the term "and/or" used in the description of the present application and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations. It should be noted that, as used herein, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or system comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or system. Without further limitations, an element defined by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article or system comprising that element.

The serial numbers of the above embodiments of the present application are for description only, and do not represent the advantages and disadvantages of the embodiments. The above is only a specific embodiment of the application, but the scope of protection of the application is not limited thereto. Any person familiar with the technical field can easily think of various equivalents within the scope of the technology disclosed in the application. Modifications or replacements, these modifications or replacements shall be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on 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.

Images