Cold start crash detection method and device, storage medium and computer equipment

Abstract

According to the cold start crash detection method and device, the storage medium and the computer equipment, when it is monitored that the target application is started, whether the target application stores the flag bit locally or not and the stored flag bit value can be detected; the flag bit value can be a first preset threshold value or a second preset threshold value, the first preset threshold value is the flag bit value set when the target application enters the home page, and the second preset threshold value is the flag bit value set when the target application is started. Therefore, if it is detected that the flag bit is not stored, it is indicated that the target application is started for the first time, and if the stored flag bit value is the first preset threshold value, it is indicated that the target application successfully enters the home page when the target application is started last time, and then it is determined that the target application does not crash when the target application is cold-started last time; and if the flag bit is stored and the stored flag bit value is a second preset threshold value, indicating that the target application does not successfully enter the home page when the target application is started last time, and further determining that the target application crashes when the target application is cold-started last time.

Description

Technical Field

[0001] The present application relates to the field of mobile application development technology, and in particular to a cold start crash detection method, device, storage medium, and computer equipment. Background Art

[0002] During mobile app development, app stability is a key indicator of user experience. However, during app launch, crashes can occur due to code defects, system compatibility issues, resource loading failures, and other factors. This is especially true during the critical phase from cold start to the homepage, where crashes can negatively impact the user's initial experience or cause service unavailability.

[0003] Currently, existing cold start crash detection methods usually rely on system logs or third-party crash monitoring tools, but these methods mainly focus on the global crash rate and cannot accurately determine whether the application crashes during the cold start process. Summary of the Invention

[0004] The purpose of this application is to solve at least one of the above-mentioned technical defects, especially the technical defect that the cold start crash detection method in the prior art usually relies on system logs or third-party crash monitoring tools and cannot accurately determine whether the application crashed during the cold start process.

[0005] The present application provides a cold start crash detection method, the method comprising:

[0006] When detecting that a target application is started, detecting whether the target application has a flag bit stored locally and the value of the stored flag bit;

[0007] If the flag bit is not stored, or the stored flag bit value is a first preset threshold, determining that the target application did not crash during the last cold start, wherein the first preset threshold is the flag bit value set when the target application enters the homepage;

[0008] If the flag is stored and the stored flag value is a second preset threshold, it is determined that the target application crashed during the last cold start, wherein the second preset threshold is the flag value set when the target application is started.

[0009] Optionally, the method further includes:

[0010] If the flag bit is not stored, or the stored flag bit value is the first preset threshold, the flag bit value of the flag bit is set to the second preset threshold when the target application is started, and the second preset threshold is saved locally.

[0011] Optionally, the method further includes:

[0012] When it is detected that the target application enters the homepage, the flag value of the flag is modified to the first preset threshold, and the first preset threshold is saved locally.

[0013] Optionally, the method further includes:

[0014] When the target application meets a preset statistical condition, the cold start crash rate of the target application is counted.

[0015] The present application also provides a cold start crash detection device, comprising:

[0016] A crash detection module is used to detect whether a flag bit is stored locally for the target application and the value of the stored flag bit when detecting that the target application is started;

[0017] a first determining module, configured to determine that the target application did not crash during the last cold start if the flag is not stored or the stored flag value is a first preset threshold, wherein the first preset threshold is the flag value set when the target application enters the homepage;

[0018] The second determination module is used to determine that the target application crashed during the last cold start if the flag is stored and the stored flag value is a second preset threshold, wherein the second preset threshold is the flag value set when the target application is started.

[0019] Optionally, the device further comprises:

[0020] The first setting module is used to set the flag value of the flag to the second preset threshold when the target application is started if the flag is not stored or the stored flag value is the first preset threshold, and save the second preset threshold locally.

[0021] Optionally, the device further comprises:

[0022] The second setting module is used to modify the flag value of the flag to the first preset threshold when monitoring that the target application enters the homepage, and save the first preset threshold locally.

[0023] Optionally, the device further comprises:

[0024] The crash rate statistics module is used to count the cold start crash rate of the target application when the target application reaches a preset statistical condition.

[0025] The present application also provides a computer-readable storage medium, which stores computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the cold start crash detection method as described in any of the above embodiments.

[0026] The present application also provides a computer device, comprising: one or more processors, and a memory;

[0027] The memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the cold start crash detection method as described in any one of the above embodiments are performed.

[0028] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0029] The cold start crash detection method, device, storage medium and computer equipment provided by the present application can detect whether the target application has a flag stored locally and the stored flag value when monitoring the startup of the target application; the flag value can be a first preset threshold value or a second preset threshold value, wherein the first preset threshold value is the flag value set when the target application enters the homepage, and the second preset threshold value is the flag value set when the target application starts. Therefore, if the present application detects that no flag is stored, it means that the target application is started for the first time. If the stored flag value is the first preset threshold value, it means that the target application successfully entered the homepage during the last startup. At this time, it can be determined that the target application did not crash during the last cold start; if a flag is stored and the stored flag value is the second preset threshold value, it means that the target application did not successfully enter the homepage during the last startup. At this time, it can be determined that the target application crashed during the last cold start. This method can not only accurately distinguish whether the target application exited normally or due to a crash, but also can directly detect whether a crash occurred during the last cold start at the next startup, thereby effectively improving the efficiency and accuracy of cold start crash detection. In addition, this method does not need to rely on a third-party SDK, which can enhance privacy protection and obtain crash information in a timely manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0031] Figure 1 A flowchart of a cold start crash detection method provided in an embodiment of the present application;

[0032] Figure 2 A schematic diagram of a target application flag setting process when a flag is not stored or a stored flag value is a first preset threshold value provided in an embodiment of the present application;

[0033] Figure 3 A schematic diagram of the flag setting process when detecting that a target application enters the homepage provided in an embodiment of the present application;

[0034] Figure 4 A schematic diagram of the structure of a cold start crash detection device provided in an embodiment of the present application;

[0035] Figure 5 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0037] In one embodiment, Figure 1 As shown, Figure 1 A schematic diagram of a cold start crash detection method provided in an embodiment of the present application is provided. The present application provides a cold start crash detection method, which may include:

[0038] S110: When it is detected that the target application is started, it is detected whether the target application has a flag bit stored locally, and the stored flag bit value.

[0039] In this step, when performing cold start crash detection on the target application, the usage of the target application may be monitored, and based on the usage of the target application, it may be determined whether the target application had a cold start crash when it was last started.

[0040] Specifically, the present application can pre-set the application that needs to be monitored as the target application, and monitor the usage of the target application. If the target application is detected to be started, it is detected whether the target application has a flag stored locally. If a flag is stored, the flag value corresponding to the flag is detected, so as to determine whether the target application crashed due to cold start during the last startup through the flag and its flag value.

[0041] When monitoring the usage of a target application, the present application can detect whether the target application is started by listening to the target application's program code. For example, when the target application is started, the system will trigger a specific startup event or callback function. The present application can obtain the startup status of the target application by listening to these events or functions. Once the target application is detected to be started, the system can begin executing the cold start crash detection process.

[0042] When the present application executes the cold start crash detection process, it can detect whether the target application has a flag bit stored locally, as well as the stored flag bit value. It is understandable that the flag bit of the present application refers to a data bit used to identify the cold start state of the target application. When the target application is started for the first time, the flag bit may not be stored locally, or the flag bit is in the initial state. As the target application runs, the flag bit will be set or modified to reflect whether the startup state of the target application is successful. The flag bit value of the present application represents the specific numerical information carried by the flag bit. It can be a binary number, a hexadecimal number or other forms of numerical representation. It can be set according to the actual situation and is not limited here.

[0043] Furthermore, to efficiently detect crashes, this application can also employ an asynchronous detection mechanism. That is, after detecting the launch of the target application, the main thread's execution is not blocked. Instead, the presence and value of the flag bit are asynchronously detected in the background. This way, even if the crash detection process takes a long time, it will not affect the normal launch and user experience of the target application.

[0044] S120: If the flag is not stored, or the stored flag value is a first preset threshold, it is determined that the target application did not crash during the last cold start, wherein the first preset threshold is the flag value set when the target application enters the homepage.

[0045] In this step, when S110 monitors the startup of the target application, it is detected whether the target application has a flag stored locally, as well as the stored flag value. If the flag is not stored, or the stored flag value is the first preset threshold, since the first preset threshold of this application is the flag value set when the target application enters the home page, the detection result can determine that the target application did not crash during the last cold start.

[0046] Specifically, after detecting whether the target application has a flag stored locally and the value of the stored flag, the present application can determine whether the target application crashed during the last cold start based on the detection result. For example, when the present application detects that the target application does not store a flag, it means that the target application may be started for the first time, and its last startup status cannot be determined at this time, so it is assumed that it did not crash during the last cold start. If it is detected that the target application has a flag stored locally, and the stored flag value is the first preset threshold, since the first preset threshold of the present application is the flag value set when the target application enters the home page, the detection result indicates that the target application successfully entered the home page during the last startup, which also means that the target application did not crash during the last cold start.

[0047] It is understandable that the first preset threshold in this application serves as a sign that the target application has successfully entered the homepage. Its setting and storage are both for the purpose of accurately determining whether the previous launch was successful upon subsequent launch. Through this judgment logic, this application can accurately distinguish whether the target application exited normally or due to a crash, thereby providing developers with a reliable cold start crash detection method.

[0048] S130: If a flag is stored and the stored flag value is a second preset threshold, it is determined that the target application crashed during the last cold start, wherein the second preset threshold is the flag value set when the target application is started.

[0049] In this step, when S110 monitors that the target application is started, it is detected whether the target application has a flag stored locally, as well as the stored flag value. If a flag is stored and the stored flag value is the second preset threshold, since the second preset threshold of this application is the flag value set when the target application is started, the detection result can be used to determine that the target application crashed during the last cold start.

[0050] Specifically, after detecting whether the target application has a flag stored locally and the value of the stored flag, the present application can determine whether the target application crashed during the last cold start based on the detection result. For example, when the present application detects that the target application has a flag stored locally and the flag value corresponding to the flag is a second preset threshold, it indicates that the target application failed to successfully enter the homepage during the last startup.

[0051] It is understandable that since the second preset threshold is set as a flag value configured when the target application is started in this application, it indicates the specific status of the target application during the startup phase. Therefore, when such a flag value is detected, it means that the target application only reached the startup phase during the last startup process and did not progress to the home page. Therefore, it can be concluded that the target application crashed during the last cold start. This judgment logic is not only intuitive and efficient, but also can accurately reveal the performance of the target application during the cold start phase, thereby helping developers to identify and fix potential problems in a timely manner.

[0052] It should be noted that in the cold start crash detection method of the present application, the flag value is set to two preset thresholds: a first preset threshold and a second preset threshold. These two preset thresholds represent the two states of the target application successfully entering the homepage and failing to enter the homepage (i.e., crashing). By reading and comparing the current value of the flag with these two preset thresholds, the present application can accurately determine whether the target application crashed during the last cold start. This method not only improves the efficiency and accuracy of cold start crash detection, but also provides developers with instant feedback, helping them to promptly fix problems that may cause application crashes, thereby improving user experience.

[0053] In the above embodiment, when the target application is detected to be started, it can be detected whether the target application has a flag stored locally, as well as the stored flag value; the flag value can be a first preset threshold value or a second preset threshold value, wherein the first preset threshold value is the flag value set when the target application enters the homepage, and the second preset threshold value is the flag value set when the target application is started. Therefore, if the present application detects that the flag is not stored, it means that the target application is started for the first time. If the stored flag value is the first preset threshold value, it means that the target application successfully entered the homepage during the last startup. At this time, it can be determined that the target application did not crash during the last cold start; if a flag is stored and the stored flag value is the second preset threshold value, it means that the target application did not successfully enter the homepage during the last startup. At this time, it can be determined that the target application crashed during the last cold start. This method can not only accurately distinguish whether the target application exited normally or due to a crash, but also directly detect whether a crash occurred during the last cold start when it is started next time, thereby effectively improving the efficiency and accuracy of cold start crash detection. In addition, this method does not need to rely on a third-party SDK, which can enhance privacy protection and obtain crash information in a timely manner.

[0054] In one embodiment, Figure 2 As shown, Figure 2 A schematic diagram of a target application flag setting process when a flag is not stored or a stored flag value is a first preset threshold provided in an embodiment of the present application; the method may further include:

[0055] S121: If the flag bit is not stored, or the stored flag bit value is the first preset threshold, the flag bit value of the flag bit is set to the second preset threshold when the target application is started, and the second preset threshold is saved locally.

[0056] In this embodiment, when the target application is started and detects that the flag bit is not stored, or the stored flag bit value is the first preset threshold, the system will perform a flag bit update operation. Specifically, the present application can set the flag bit value to the second preset threshold and save this new value to local storage. The purpose of this step is to set a clear flag for the current startup cycle of the target application so that in the subsequent detection process, it can be accurately distinguished whether the target application has successfully entered the homepage.

[0057] For example, when this application starts the target application, it is not detected that the target application has a flag stored locally, or it is detected that the target application has a flag stored this time, and the flag value is 1, that is, the first preset threshold, then it means that the target application did not experience a cold start crash when it was last started. At this time, this application can reset the flag value in the target application, such as changing the flag value 1 to 0, that is, the second preset threshold, to indicate that the target application is currently in the startup state.

[0058] This design not only improves the flexibility of cold start crash detection, but also ensures the accuracy and reliability of the detection results. In addition, by saving the flag value to local storage, the system can quickly read the last set flag value when the target application is next started, thereby further improving detection efficiency.

[0059] In one embodiment, Figure 3 A schematic diagram of a flag setting process when detecting that a target application enters the homepage is provided in an embodiment of the present application; the method may further include:

[0060] S140: When it is detected that the target application enters the homepage, the flag value of the flag is modified to a first preset threshold, and the first preset threshold is saved locally.

[0061] In this embodiment, after the target application successfully enters the homepage, the application can perform another key flag update operation. Specifically, the application can modify the current value of the flag to a first preset threshold and save this new value to local storage. The purpose of this step is to confirm that the target application has successfully entered the homepage, thereby setting a success flag for the current startup cycle of the target application.

[0062] For example, when this application detects that the target application has successfully loaded and displayed the homepage content, it means that the target application has successfully completed the startup process and no cold start crash has occurred. Therefore, this application can change the previously set flag value to the first preset threshold, that is, the flag value when the target application enters the homepage, and save this new flag value to local storage. In this way, the next time the target application is started, the system can quickly determine whether the target application successfully entered the homepage during the last startup by reading this flag value.

[0063] Furthermore, in this application, when monitoring whether the target application enters the homepage, since the APP will first enter its entry function when it starts, and this entry function usually contains a lot of initialization work, such as various initialization operations required in the APP. Once these steps are completed, the system will call the lifecycle method of the homepage page in sequence, obtain the homepage display data, and render the data. Once the page lifecycle is completed, it is considered to have successfully entered the homepage.

[0064] Based on this, this application can determine whether a flag is stored locally starting from the first line of code in the APP entry function. If not stored, it is determined to be the first startup after the APP is installed, and there is no crash at this time. If the flag is stored and its value is 1, it means that no crash occurred during the last startup; if the value is 0, it indicates that a crash occurred during the last startup, and the flag value is reset to 0. When the home page is successfully entered, the flag value is set to 1; if the home page is not entered, the flag remains set to 0 at startup. This application determines whether the target application crashed during the last startup through changes in the flag value, thereby effectively improving the detection efficiency and accuracy of cold start crashes.

[0065] This design not only further improves the accuracy and reliability of cold start crash detection, but also provides developers with a more intuitive and convenient crash detection method. Developers only need to check the value of the flag bit to quickly understand the target application's performance during the cold start phase, thereby promptly identifying and fixing problems that may cause application crashes.

[0066] In one embodiment, the method may further include:

[0067] S150: When the target application meets a preset statistical condition, the cold start crash rate of the target application is counted.

[0068] In this embodiment, in order to more comprehensively evaluate the stability and performance of the target application, this application also introduces a statistical mechanism for the cold start crash rate. Specifically, when this application detects that the target application has reached a preset statistical condition, it can start the crash rate calculation process. The preset statistical conditions here can be flexibly set according to actual needs. For example, it can be that the target application has been started a certain number of times, has run for a specific length of time, or is within a specific time period, etc. The specific setting can be based on the actual situation and is not limited here.

[0069] When calculating the cold start crash rate, this application can review all launch records of the target application, particularly those related to cold start crashes. By comparing the number of successful launches of the target application with the number of failed launches due to crashes, this application can calculate the cold start crash rate, which is the ratio of cold start crashes to total launches. This metric can intuitively reflect the stability and reliability of the target application during the cold start phase.

[0070] Furthermore, the application can also compare the calculated cold start crash rate with historical data to observe the changing trend of the crash rate. If the crash rate continues to rise, it may mean that there are some problems in the target application that need to be fixed. Conversely, if the crash rate shows a downward trend, it indicates that the stability of the target application is improving.

[0071] Through such statistics and analysis, this application not only provides developers with quantitative indicators of the target application's cold start performance, but also helps them promptly identify and resolve potential issues. This helps improve the overall quality and user experience of the target application, while also helping developers gain confidence in the application's stability and performance.

[0072] The cold start crash detection device provided in an embodiment of the present application is described below. The cold start crash detection device described below and the cold start crash detection method described above can refer to each other.

[0073] In one embodiment, Figure 4 As shown, Figure 4 This is a schematic diagram of the structure of a cold start crash detection device provided in an embodiment of the present application. The present application also provides a cold start crash detection device, which may include a crash detection module 210, a first determination module 220, and a second determination module 230, specifically including the following:

[0074] The crash detection module 210 is configured to detect whether a flag bit is stored locally for the target application and the value of the stored flag bit when detecting that the target application is started.

[0075] The first determination module 220 is used to determine that the target application did not crash during the last cold start if the flag is not stored or the stored flag value is a first preset threshold, wherein the first preset threshold is the flag value set when the target application enters the homepage.

[0076] The second determination module 230 is used to determine that the target application crashed during the last cold start if the flag is stored and the stored flag value is a second preset threshold, wherein the second preset threshold is the flag value set when the target application is started.

[0077] In the above embodiment, when the target application is detected to be started, it can be detected whether the target application has a flag stored locally, as well as the stored flag value; the flag value can be a first preset threshold value or a second preset threshold value, wherein the first preset threshold value is the flag value set when the target application enters the homepage, and the second preset threshold value is the flag value set when the target application is started. Therefore, if the present application detects that the flag is not stored, it means that the target application is started for the first time. If the stored flag value is the first preset threshold value, it means that the target application successfully entered the homepage during the last startup. At this time, it can be determined that the target application did not crash during the last cold start; if a flag is stored and the stored flag value is the second preset threshold value, it means that the target application did not successfully enter the homepage during the last startup. At this time, it can be determined that the target application crashed during the last cold start. This method can not only accurately distinguish whether the target application exited normally or due to a crash, but also directly detect whether a crash occurred during the last cold start when it is started next time, thereby effectively improving the efficiency and accuracy of cold start crash detection. In addition, this method does not need to rely on a third-party SDK, which can enhance privacy protection and obtain crash information in a timely manner.

[0078] In one embodiment, the apparatus may further include:

[0079] The first setting module is used to set the flag value of the flag to the second preset threshold when the target application is started if the flag is not stored or the stored flag value is the first preset threshold, and save the second preset threshold locally.

[0080] In one embodiment, the apparatus may further include:

[0081] The second setting module is used to modify the flag value of the flag to the first preset threshold when monitoring that the target application enters the homepage, and save the first preset threshold locally.

[0082] In one embodiment, the apparatus may further include:

[0083] The crash rate statistics module is used to count the cold start crash rate of the target application when the target application reaches a preset statistical condition.

[0084] In one embodiment, the present application also provides a computer-readable storage medium, which stores computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the cold start crash detection method as described in any of the above embodiments.

[0085] In one embodiment, the present application further provides a computer device, including: one or more processors, and a memory.

[0086] The memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the cold start crash detection method as described in any one of the above embodiments are performed.

[0087] Schematically, as Figure 5 As shown, Figure 5 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. The computer device 300 can be provided as a server. Figure 5 Computer device 300 includes a processing component 302, which further includes one or more processors, and a memory resource represented by memory 301 for storing instructions executable by processing component 302, such as an application. The application stored in memory 301 may include one or more modules, each corresponding to a set of instructions. In addition, processing component 302 is configured to execute the instructions to perform the cold boot crash detection method of any of the above embodiments.

[0088] The computer device 300 may further include a power supply component 303 configured to perform power management of the computer device 300, a wired or wireless network interface 304 configured to connect the computer device 300 to a network, and an input / output (I / O) interface 305. The computer device 300 may operate based on an operating system stored in the memory 301, such as Windows Server™, Mac OS X™, Unix™, Linux™, Free BSD™, or the like.

[0089] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0090] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0091] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referenced to each other.

[0092] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A cold start crash detection method, characterized in that: The method comprises: When detecting that a target application is started, detecting whether the target application has a flag bit stored locally and the value of the stored flag bit; If the flag bit is not stored, or the stored flag bit value is a first preset threshold, determining that the target application did not crash during the last cold start, wherein the first preset threshold is the flag bit value set when the target application enters the homepage; If the flag is stored and the stored flag value is a second preset threshold, it is determined that the target application crashed during the last cold start, wherein the second preset threshold is the flag value set when the target application is started.

2. The cold start crash detection method according to claim 1, characterized in that: The method further comprises: If the flag bit is not stored, or the stored flag bit value is the first preset threshold, the flag bit value of the flag bit is set to the second preset threshold when the target application is started, and the second preset threshold is saved locally.

3. The cold start crash detection method according to claim 1 or 2, characterized in that: The method further comprises: When it is detected that the target application enters the homepage, the flag value of the flag is modified to the first preset threshold, and the first preset threshold is saved locally.

4. The cold start crash detection method according to claim 1 or 2, characterized in that: The method further comprises: When the target application meets a preset statistical condition, the cold start crash rate of the target application is counted.

5. A cold start crash detection device, characterized in that: include: A crash detection module is used to detect whether a flag bit is stored locally for the target application and the value of the stored flag bit when detecting that the target application is started; a first determining module, configured to determine that the target application did not crash during the last cold start if the flag is not stored or the stored flag value is a first preset threshold, wherein the first preset threshold is the flag value set when the target application enters the homepage; The second determination module is used to determine that the target application crashed during the last cold start if the flag is stored and the stored flag value is a second preset threshold, wherein the second preset threshold is the flag value set when the target application is started.

6. The cold start crash detection device according to claim 5, characterized in that: The device further comprises: The first setting module is used to set the flag value of the flag to the second preset threshold when the target application is started if the flag is not stored or the stored flag value is the first preset threshold, and save the second preset threshold locally.

7. The cold start crash detection device according to claim 5 or 6, characterized in that: The device further comprises: The second setting module is used to modify the flag value of the flag to the first preset threshold when monitoring that the target application enters the homepage, and save the first preset threshold locally.

8. The cold start crash detection device according to claim 5 or 6, characterized in that: The device further comprises: The crash rate statistics module is used to count the cold start crash rate of the target application when the target application reaches a preset statistical condition.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the cold boot crash detection method according to any one of claims 1 to 4.

10. A computer device, characterized in that: include: one or more processors, and memory; The memory stores computer-readable instructions, which, when executed by the one or more processors, perform the steps of the cold boot crash detection method according to any one of claims 1 to 4.

Images