Application crash processing method, apparatus, device, and medium

Abstract

Embodiments of the present disclosure disclose an application crash processing method and device, equipment and medium, in the case of monitoring a crash event in the process of displaying an advertisement by an application, obtaining advertisement attribute information of the advertisement, live information of the crash event and device attribute information of a terminal device running the application; determining whether a webview performance problem occurs according to the live information of the crash event; in the case of the webview performance problem, determining a cause of the webview performance problem according to the advertisement attribute information of the advertisement, the live information of the crash event and the device attribute information of the terminal device; and shielding the advertisement according to the cause of the webview performance problem. The influence of the webview performance problem on advertisement revenue can be reduced.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and more specifically, to an application crash handling method, apparatus, device, and medium. Background Technology

[0002] Currently, most mobile ads utilize WebView for rendering. In aggregated advertising, the platform combines ads from various third-party sources. As ad requests increase, WebView performance issues become increasingly apparent. However, because each third-party ad source is managed through its own WebView, it's a black box to the aggregation platform. This makes it impossible to effectively monitor all WebViews, hindering timely identification and resolution of issues when mobile applications crash during ad display. This impacts not only ad revenue but also user experience, leading to user churn. Summary of the Invention

[0003] This disclosure provides an application crash handling method, apparatus, device, and medium that can reduce the impact of webview performance issues on advertising revenue.

[0004] According to a first aspect of the present disclosure, an application crash handling method is provided, the method comprising:

[0005] If a crash event is detected during the display of an advertisement in the application, the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device running the application are obtained.

[0006] Based on the on-site information of the crash event, determine whether a webview performance issue has occurred;

[0007] In the event of a WebView performance problem, the cause of the WebView performance problem is determined based on the advertisement attribute information of the advertisement, the on-site information of the crash event, and the device attribute information of the terminal device.

[0008] Based on the cause of the webview performance problem, the advertisement is blocked.

[0009] According to a second aspect of this disclosure, an application crash handling method is provided, the apparatus comprising:

[0010] The acquisition module is used to acquire, when a crash event is detected during the display of an advertisement in the application, the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device running the application.

[0011] The first determining module is used to determine whether a webview performance problem has occurred based on the on-site information of the crash event;

[0012] The second determining module is used to determine the cause of the webview performance problem based on the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device when a webview performance problem occurs.

[0013] A blocking module is used to block the advertisement based on the cause of the webview performance problem.

[0014] According to a third aspect of this disclosure, an electronic device is provided, comprising a memory and a processor, the memory being configured to store executable instructions; the processor being configured to execute, under the control of the instructions, the application crash handling method described in the first aspect above.

[0015] According to a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the application crash handling method as described in the first aspect of this disclosure.

[0016] According to the application crash handling method, apparatus, device, and medium of this disclosure, when an application detects a crash event during the display of an advertisement, the electronic device acquires the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device running the application. If it is determined that a webview performance problem has occurred based on the scene information of the crash event, the device further locates the cause of the webview performance problem and then blocks the advertisement based on the cause of the webview performance problem, thereby achieving the purpose of solving the webview performance problem. By blocking the advertisement, the scope and duration of the affected users are reduced, and the impact of the webview performance problem on advertising revenue is reduced.

[0017] Other features and advantages of this disclosure will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the present disclosure and, together with their description, serve to explain the principles of the present disclosure.

[0019] Figure 1 This is a schematic flowchart of an application crash handling method according to an embodiment of the present disclosure;

[0020] Figure 2This is an interactive diagram illustrating an application crash handling method according to an example of this disclosure;

[0021] Figure 3 This is a schematic block diagram of an application crash handling apparatus according to an embodiment of the present disclosure;

[0022] Figure 4 This is a block diagram of the hardware configuration of an electronic device according to embodiments of the present disclosure. Detailed Implementation

[0023] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0024] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0025] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0026] In all the examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0027] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0028] <Method Implementation>

[0029] In this embodiment, an application crash handling method is provided. This method can be implemented by an electronic device, which can be a server or a terminal device. That is, the method in this embodiment can be implemented by a server, a terminal device, or both.

[0030] In applications where the method in this embodiment is implemented with the participation of a terminal device, the interaction may include human-computer interaction. In applications where the method in this embodiment is implemented with the participation of a server, the interaction may include interaction between the server and the terminal device.

[0031] Step S1100: If a crash event is detected during the display of an advertisement in the application, obtain the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device running the application.

[0032] In this embodiment, the application can be an advertising aggregation application that can aggregate third-party advertising SDKs (Software Development Kits), such as Google Ads SDK, Facebook Ads SDK, etc. The application can be installed and run on a terminal device, and its version on different terminal devices can be the same or different.

[0033] In this embodiment, a crash event can be any exception that occurs during application execution, such as the application crashing while displaying an advertisement, the advertisement page becoming unresponsive, or non-operationally returning to the previous page. In this embodiment, crash events during the application's advertisement display process can be monitored through a crash event capture function. The crash event capture function may be the same or different on different operating systems, and this embodiment does not impose any limitations.

[0034] In this embodiment, the advertising attribute information of the advertisement includes at least one of the following: the advertising source of the advertisement, the identifier of the advertising unit in which the advertisement is located, the advertising type of the advertisement, the identifier of the advertisement, the title of the advertisement, the advertising material of the advertisement, and the webview content of the advertisement.

[0035] The advertising source for the above advertisement refers to the source of the advertisement, such as the Google Ads SDK, Facebook Ads SDK, etc.

[0036] The above AdUnit refers to a specific ad placement. When configuring or generating a third-party ad placement ID, corresponding ad format, a set of base prices, and the priority of the ad unit in the strategy at this level, the identifier of the ad unit can be the sorting number of the ad unit in the ad unit list (Waterfall), where the ad unit list is a priority list of ad units.

[0037] The above ad types include, but are not limited to, banner ads, native ads, interstitial ads, and rewarded ads. Each ad is uniquely identified by its identifier, distinguishing it from other ads. The ad title is the main name of the ad. The ad creative is the content of the ad itself. The webview content can be the webview's URL or HTML text.

[0038] In this embodiment, the device attribute information may be the device's webview version, system version, device manufacturer, device model, network type, etc. When the terminal device is a mobile phone, the device attribute information of the mobile phone may include, but is not limited to, the mobile phone's webview version, system version, mobile phone manufacturer, mobile phone model, network type, etc.

[0039] In this embodiment, the on-site information of the crash event includes, but is not limited to, thread information, crash thread name, memory usage, system logs, crash type (Java crash, native crash), crash native library, crash stack, etc.

[0040] In this embodiment, combined with Figure 2 As shown, when an application on a terminal device crashes abnormally, the ad page becomes unresponsive, or the user is abnormally redirected to the previous page during the display of an ad, the terminal device can obtain the ad's attribute information, the crash event's on-site information, and the terminal device's device attribute information. Then, it can locate the problem based on the ad's attribute information, the crash event's on-site information, and the terminal device's device attribute information.

[0041] In this embodiment, step S1100, which involves obtaining the advertising attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device running the application, may further include: after the terminal device sends an advertisement request to the third-party advertising SDK through the application, the third-party advertising SDK will return the advertisement view of the advertisement, and the terminal device can then traverse the advertisement view to obtain the advertising attribute information of the advertisement.

[0042] For example, to obtain the webview content of an advertisement, when the terminal device sends an advertisement request to the Google Ads SDK through the application, the Google Ads SDK will return the advertisement view of the advertisement. The terminal device can then traverse the advertisement view, find the webview, and then obtain the content of the webview by inserting a JS script, thereby obtaining the URL of the webview or the HTML text of the webview, etc.

[0043] If a crash event is detected during the display of an advertisement in the application, after obtaining the advertisement attribute information of the advertisement, the on-site information of the crash event, and the device attribute information of the terminal device running the application, proceed as follows:

[0044] Step S1200: Based on the on-site information of the crash event, determine whether a webview performance problem has occurred.

[0045] In this embodiment, after obtaining the advertising attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device, the terminal device can report the advertising attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device to the application performance management (APM) system. The APM system can then determine whether a webview performance problem has occurred based on the scene information of the crash event. The APM system can be located on a server.

[0046] In this embodiment, determining whether a webview performance problem has occurred based on the on-site information of the crash event in step S1200 may further include: determining that a webview performance problem has occurred if the on-site information of the crash event includes a set keyword; wherein the set keyword includes at least one of the following: webview, chrome, chromium.

[0047] In an alternative embodiment, such as Figure 2 As shown, after the APM system collects the ad attribute information, the crash event scene information, and the terminal device attribute information, it can check whether any of the following in the crash event scene information, such as the crash native library, crash stack, or crash thread name, contains the keywords "webview," "chrome," or "chromium." If any of the following contains the keywords "webview," "chrome," or "chromium," it can be considered that a webview performance problem has occurred.

[0048] After determining whether a webview performance issue has occurred based on the on-site information of the crash event, proceed to:

[0049] Step S1300: In the event of a webview performance problem, determine the cause of the webview performance problem based on the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device.

[0050] In this embodiment, when the APM system determines that a webview performance problem has occurred, since the APM system can only analyze white-box performance problems, while webviews only experience black-box performance problems, the APM system also needs to further report the advertising attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device to the information analysis system for analysis and processing. This information analysis system can be located on the server.

[0051] In this embodiment, in step S1300, when a webview performance problem occurs, determining the cause of the webview performance problem based on the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device may further include the following steps S1310 to S1330:

[0052] Step S1310: In the event of a webview performance problem, extract key information from the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device.

[0053] In step S1310, after the information analysis system obtains the advertising attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device, it will aggregate the advertising attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device, and extract the key information of the aggregated advertising attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device.

[0054] Key information can be extracted from the above-mentioned advertising attribute information, crash event scene information, and device attribute information. This key information can be a single keyword or a series of keywords. Taking the memory leak information in the system log as an example, the single keyword can be memory or leak, and the series of keywords can be memory leak.

[0055] For example, after aggregating and extracting key information such as advertising attribute information, crash event scene information, and terminal device attribute information, the extracted key information might include device model and system logs. For instance, if the JavaScript code in the webview is poorly written, it might cause a memory leak after execution. In this case, the keyword "memory leak" would appear very frequently in the system log, making it a key piece of information. Alternatively, both memory usage and the leak could be considered key information. Furthermore, analyzing the frequency of this memory leak across different device models would also provide another key piece of information.

[0056] Step S1320: Determine the frequency of occurrence of the extracted key information by combining historical data in the database.

[0057] The historical data includes the application's running data on different terminal devices within a recently defined time period. This running data includes, but is not limited to, data on the application displaying advertisements on different terminal devices. This data can be advertisement attribute information, crash event scene information, and terminal device attribute information. The recently defined time period can be the most recent day, the most recent week, etc. That is, the database can store data indexed by day or by week; this embodiment does not impose any limitations.

[0058] In step S1320, after identifying the key information, the frequency of occurrence of the key information can be determined by combining it with historical data in the database.

[0059] Continuing the example above, after identifying "memory" as a single keyword, "leak" as a single keyword, "memory leak" as a consecutive keyword, and "device model" as a keyword, we can combine this with historical data from the database for the most recent day to determine the frequency P of the "memory" keyword, the frequency Q of the "leak" keyword, the frequency N of the "memory leak" keyword, the frequency M of device model 1 corresponding to the memory leak, the frequency P of device model 2, and so on. Alternatively, we can also determine the frequency of the device model corresponding to the "memory" keyword, and the frequency of the device model corresponding to the "leak" keyword.

[0060] Step S1330: Sort the frequency of occurrence of the key information and locate the cause of the webview performance problem based on the sorting result.

[0061] Continuing the example above, we can first sort the frequency N of the key information "memory leak" in descending order, and then further sort the frequency of the corresponding device models in descending order. For example, it could be M for device model 1, P for device model 2, and so on. If device model 1 has the highest frequency of memory leaks, then we can determine that the cause of the WebView performance problem is incompatibility between the advertisement and the device's attributes. Of course, the cause of the WebView performance problem could also be the advertisement's creative elements, etc.

[0062] In the event of a WebView performance issue, after determining the cause of the WebView performance problem based on the advertisement attribute information, the scene information of the crash event, and the device attribute information of the terminal device, proceed as follows:

[0063] Step S1400: Based on the cause of the webview performance problem, block the advertisement.

[0064] In this embodiment, after determining the cause of the webview performance problem, the advertisement can be blocked according to the corresponding strategy, thereby reducing the scope and duration of the affected users, improving user experience and retention, and reducing the impact of performance problems on advertising revenue.

[0065] In one example, blocking the advertisement in step S1400 based on the cause of the webview performance problem may further include: if the cause of the webview performance problem is the advertisement's creative material, prohibiting the advertisement from being sent to the application.

[0066] In this example, such as Figure 2 As shown, when the information analysis system identifies the ad creative as the cause of the webview performance issue, the corresponding ad aggregation backend of the application, after finding the corresponding ad based on its identifier, directly blocks the delivery of that ad to the application. Alternatively, the ad backend of the third-party ad SDK to which the ad belongs, after finding the corresponding ad based on its identifier, directly blocks the delivery of that ad to the application through the ad aggregation platform. In both cases, the ad aggregation backend runs on a server. That is, when the ad creative is accurately identified, the ad is blocked directly by prohibiting its delivery.

[0067] In one example, step S1400, based on the cause of the webview performance problem, may further include: if the cause of the webview performance problem is that the advertisement is incompatible with the device attribute information of the terminal device, providing a configuration interface; changing the global configuration and waterfall list for the target device through the configuration interface to remove the advertisement unit corresponding to the advertisement source from the corresponding waterfall list; wherein, the target device is a terminal device that conforms to the device attribute information and runs the application.

[0068] The configuration interface can be any entry point that allows users to input information, such as an input box, drop-down list, or voice input entry; there are no restrictions here. The global configuration applies globally. The waterfall list has already been described in the previous embodiments and will not be repeated here.

[0069] In this example, such as Figure 2As shown, when the information analysis system identifies the cause of the webview performance issue as incompatibility between the advertisement and device attribute information, it can use the configuration interface provided by the aggregated advertising backend to modify the global configuration and waterfall list for the specific device model running the application. This allows the problematic AND ad unit to be removed from the corresponding waterfall list. In other words, by modifying the global configuration and waterfall list for terminal devices that meet the mobile phone characteristics and are running the application, the system removes the ad unit corresponding to the third-party advertising SDK to which the problematic advertisement belongs from the corresponding waterfall list, thereby disabling that third-party advertising SDK.

[0070] According to embodiments of this disclosure, when an application detects a crash during the display of an advertisement, the electronic device obtains the advertisement attribute information, the scene information of the crash event, and the device attribute information of the terminal device running the application. If a webview performance problem is determined based on the scene information of the crash event, the device further locates the cause of the webview performance problem and then blocks the advertisement based on the cause of the webview performance problem, thereby resolving the webview performance problem. By blocking the advertisement, the scope and duration of the affected users are reduced, and the impact of the webview performance problem on advertising revenue is also reduced.

[0071] In one embodiment, after blocking the advertisement according to the cause of the webview performance problem in step S1400 above, the application crash handling method of this disclosure embodiment further includes: stopping the step of blocking the advertisement when the advertisement is not displayed within a set time period.

[0072] The time period can be set according to the actual application scenario and actual needs. The time period can be one month, one week, etc.

[0073] In this embodiment, if the advertisement that caused the webview performance problem no longer appears within a set time period, the previous blocking strategy can be canceled, that is, the advertisement can be stopped from being blocked, so that the advertisement can be displayed normally.

[0074] The following example demonstrates an application crash handling method, which combines... Figure 2 As shown, the application crash handling methods may include:

[0075] Step S2100: If a crash event is detected during the display of an advertisement in the application, the application obtains the advertisement attribute information, the scene information of the crash event, and the device attribute information of the terminal device running the application and reports them to the APM system.

[0076] Step S2200: If the APM system detects that the crash native library, crash stack, and crash thread name in the crash event's on-site information include webview, chrome, or chromium, it determines that a webview performance problem has occurred and sends the information reported by the application to the information analysis system.

[0077] In step S2300, the information analysis system aggregates the reported information and extracts individual keywords and consecutive keywords from the aggregated information.

[0078] In step S2400, the information analysis system sorts the occurrence counts of extracted single keywords and consecutive keywords based on historical data in the database, and locates the cause of the webview performance problem based on the sorting results.

[0079] In step S2500, if the cause of the webview performance problem is the advertising creative of the advertisement, the aggregated advertising platform corresponding to the application will find the corresponding advertisement based on the advertisement's identifier and directly prevent the advertisement from being sent to the application. Alternatively, the advertising backend corresponding to the third-party advertising SDK to which the advertisement belongs will find the corresponding advertisement based on the advertisement's identifier and directly prevent the advertisement from being sent to the application through the aggregated advertising platform.

[0080] Step S2600: If the cause of the webview performance problem is incompatibility between the advertisement and the device attribute information of the terminal device, a configuration interface is provided; the global configuration and waterfall list are changed for the target device through the configuration interface to remove the advertisement unit corresponding to the advertisement source from the corresponding waterfall list.

[0081] This example demonstrates how to quickly and effectively analyze the direct cause of performance issues in black-box webviews. By mitigating these issues, the scope and duration of the impact on users are reduced, improving user experience and retention, while also minimizing the impact of performance problems on advertising revenue.

[0082] <Device Embodiment>

[0083] In this embodiment, an application crash handling device 3000 is also provided, such as... Figure 3As shown, the device 3000 may include an acquisition module 3100, a first determination module 3200, a second determination module 3300, and a shielding module 3400.

[0084] The acquisition module 3100 is used to acquire, when a crash event is detected during the display of an advertisement in the application, the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device running the application.

[0085] The first determining module 3200 is used to determine whether a webview performance problem has occurred based on the on-site information of the crash event.

[0086] The second determining module 3300 is used to determine the cause of the webview performance problem based on the advertisement attribute information of the advertisement, the scene information of the crash event, and the device attribute information of the terminal device when a webview performance problem occurs.

[0087] The blocking module 3400 is used to block the advertisement based on the cause of the webview performance problem.

[0088] Those skilled in the art will understand that the application crash handling device 3000 can be implemented in various ways. For example, the application crash handling device 3000 can be implemented by configuring the processor with instructions. For example, the instructions can be stored in ROM, and when the device is started, the instructions can be read from ROM into the programmable device to implement the application crash handling device 3000. For example, the application crash handling device 3000 can be embedded in a special-purpose device (e.g., an ASIC). The application crash handling device 3000 can be divided into independent units, or they can be combined together. The application crash handling device 3000 can be implemented by one of the various implementation methods described above, or by a combination of two or more of the various implementation methods described above.

[0089] In this embodiment, the application crash handling device 3000 can have various implementation forms. For example, the application crash handling device 3000 can be any software product or functional module running in an application that provides an application crash method, or peripheral embeddings, plug-ins, patches, etc. of these software products or applications, or it can be the software products or applications themselves.

[0090] <Equipment Example>

[0091] This disclosure provides an electronic device 4000, which can be a server or a terminal device. The server can be a monolithic server or a distributed server spanning multiple computers or a computer data center. The terminal device can be a mobile phone, tablet computer, laptop computer, etc.

[0092] like Figure 4 As shown, the electronic device 4000 includes a processor 4100 and a memory 4200. The memory 4200 stores computer instructions. When the computer instructions are executed by the processor 4100, they implement the application crash handling method provided in any of the foregoing embodiments.

[0093] Each module of the above electronic device can be implemented by the computer instructions stored in the memory running by the processor 4100, or by other circuit structures, which are not limited here.

[0094] The electronic device can be an electronic product with a processor and memory. For example, it can be a smartphone, laptop, desktop computer, tablet computer, etc.

[0095] <Media Example>

[0096] This disclosure provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the application crash handling method provided in any of the foregoing embodiments.

[0097] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions. It will be known to those skilled in the art that implementation in hardware, implementation in software, and implementation in a combination of software and hardware are equivalent.

[0098] The various embodiments of this disclosure have been described above. These descriptions are exemplary and not exhaustive, and are not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or technical improvements to the embodiments in the market, or to enable others skilled in the art to understand the embodiments disclosed herein. The scope of this disclosure is defined by the appended claims.

Claims

1. An application crash processing method, the method comprising: in the case of monitoring a crash event in the process of displaying an advertisement by an application, obtaining advertisement attribute information of the advertisement, on-site information of the crash event, and device attribute information of a terminal device running the application; determining whether a webview performance problem occurs according to the on-site information of the crash event; in the case of the occurrence of the webview performance problem, determining a cause of the webview performance problem according to the advertisement attribute information of the advertisement, the on-site information of the crash event, and the device attribute information of the terminal device; screening the advertisement according to the cause of the webview performance problem; wherein, in the case of the occurrence of the webview performance problem, the determining of the cause of the webview performance problem according to the advertisement attribute information of the advertisement, the on-site information of the crash event, and the device attribute information of the terminal device comprises: in the case of the occurrence of the webview performance problem, extracting key information in the advertisement attribute information of the advertisement, the on-site information of the crash event, and the device attribute information of the terminal device; determining the number of occurrences of the extracted key information in combination with historical data in a database; sorting the number of occurrences of the key information, and positioning the cause of the webview performance problem according to the sorting result.

2. The method of claim 1, wherein, The advertisement attribute information of the advertisement comprises at least one of the following: an advertisement source of the advertisement, an identifier of an advertisement unit where the advertisement is located, an advertisement type of the advertisement, an identifier of the advertisement, a title of the advertisement, advertisement material of the advertisement, and webview content of the advertisement.

3. The method of claim 1, wherein, The on-site information of the crash event comprises at least one of the following: a crashed native library, a crash stack, and a crash thread name. The determining of whether the webview performance problem occurs according to the on-site information of the crash event comprises: in the case of the on-site information of the crash event comprising a set keyword, determining that the webview performance problem occurs; wherein, the set keyword comprises at least one of the following: webview, chrome, and chromium.

4. The method of claim 1, wherein, The historical data comprises running data of the application on different terminal devices in a recent set time period.

5. The method of claim 1, wherein, The advertisement attribute information of the advertisement comprises an identifier of the advertisement. The screening of the advertisement according to the cause of the webview performance problem comprises: in the case of the advertisement material of the advertisement being the cause of the webview performance problem, prohibiting the advertisement from being issued to the application for display.

6. The method of claim 1, wherein, The screening of the advertisement according to the cause of the webview performance problem comprises: in the case of the advertisement being incompatible with the device attribute information of the terminal device being the cause of the webview performance problem, providing a configuration interface. The global configuration and the waterfall list are changed for a target device through the configuration interface to remove the advertisement unit corresponding to the advertisement source of the advertisement from the corresponding waterfall list. The target device is a terminal device that meets the device attribute information and runs the application program.

7. The method of any one of claims 1 to 6, wherein, After the advertisement is shielded according to the cause of the webview performance problem, the method further includes: If the advertisement is not displayed within a set time period, the step of shielding the advertisement is stopped.

8. An application crash handling apparatus, wherein, The device includes: An acquisition module configured to acquire advertisement attribute information of the advertisement, live information of the crash event, and device attribute information of a terminal device running the application program if a crash event is monitored during the process of displaying the advertisement by the application program; A first determination module configured to determine whether a webview performance problem occurs according to the live information of the crash event; A second determination module configured to determine a cause of the webview performance problem according to the advertisement attribute information of the advertisement, the live information of the crash event, and the device attribute information of the terminal device if the webview performance problem occurs; A shielding module configured to shield the advertisement according to the cause of the webview performance problem. The second determination module is specifically configured to extract key information in the advertisement attribute information of the advertisement, the live information of the crash event, and the device attribute information of the terminal device if the webview performance problem occurs; determine the number of occurrences of the extracted key information in combination with historical data in a database; sort the number of occurrences of the key information, and locate the cause of the webview performance problem according to a sorting result.

9. An electronic device, comprising: An application program crash processing method according to any one of claims 1-7.

10. A computer readable storage medium having stored thereon a computer program, the computer program, when executed by a processor, implementing the application program crash processing method according to any one of claims 1-7.

Images