CN112306833A - Application program crash statistical method and device, computer equipment and storage medium - Google Patents
Application program crash statistical method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112306833A CN112306833A CN202011173313.9A CN202011173313A CN112306833A CN 112306833 A CN112306833 A CN 112306833A CN 202011173313 A CN202011173313 A CN 202011173313A CN 112306833 A CN112306833 A CN 112306833A
- Authority
- CN
- China
- Prior art keywords
- crash
- target
- stack description
- classification
- application program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007619 statistical method Methods 0.000 title description 4
- 238000000034 method Methods 0.000 claims abstract description 54
- 238000000605 extraction Methods 0.000 claims description 9
- 238000012545 processing Methods 0.000 claims description 7
- 238000013507 mapping Methods 0.000 claims description 4
- 230000004044 response Effects 0.000 claims description 2
- 230000015556 catabolic process Effects 0.000 description 26
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 230000003287 optical effect Effects 0.000 description 6
- 230000002159 abnormal effect Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 5
- 230000008439 repair process Effects 0.000 description 4
- 238000013024 troubleshooting Methods 0.000 description 3
- 239000000284 extract Substances 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3452—Performance evaluation by statistical analysis
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Probability & Statistics with Applications (AREA)
- Evolutionary Biology (AREA)
- Bioinformatics & Computational Biology (AREA)
- Computer Hardware Design (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Life Sciences & Earth Sciences (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses a method and a device for counting collapse of an application program, computer equipment and a storage medium. The method comprises the following steps: acquiring a crash event of an application program reported by a client, and extracting crash stack description information included in the crash event, wherein the crash stack description information includes at least one crash stack description item; extracting at least one target crash stack description item associated with a service code from the crash stack description information; and performing crash statistics on the application program according to each target crash stack description item. By using the technical scheme of the invention, the collapse statistics of the application program based on the stack information can be realized, so that the occurrence reason of the collapse is more intuitively reflected, and the repairing efficiency of the application program is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method and a device for statistics of collapse of an application program, computer equipment and a storage medium.
Background
With the continuous development of the mobile internet, various mobile terminal application programs emerge from the market, and various service requirements of people in daily life are met. The application program may crash in the running process, after the crash occurs, the terminal generally reports crash information to the server, and the server performs statistics and classification on each crash information uploaded by each terminal, so that a worker on the server side can repair the application program in time.
In the prior art, the statistical classification of crash information is mainly performed according to the bottom cause of crash, for example, the bottom cause of crash may be an array boundary crossing or a process killing signal. In the prior art, the method for classifying and counting the crash according to the underlying reason can only reflect the attribute of the crash, and cannot position the abnormal service code.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a storage medium for application program crash statistics, which are used for realizing the crash statistics of an application program based on stack information, so that the occurrence reason of the crash can be reflected more visually, and the repair efficiency of the application program can be improved.
In a first aspect, an embodiment of the present invention provides a method for statistics of application crash, where the method includes:
acquiring a crash event of an application program reported by a client, and extracting crash stack description information included in the crash event, wherein the crash stack description information includes at least one crash stack description item;
extracting at least one target crash stack description item associated with a service code from the crash stack description information;
and performing crash statistics on the application program according to each target crash stack description item.
In a second aspect, an embodiment of the present invention further provides an apparatus for statistics of crash of an application, including:
the system comprises a crash stack description information extraction module, a crash stack description information extraction module and a data processing module, wherein the crash stack description information extraction module is used for acquiring a crash event of an application program reported by a client and extracting crash stack description information included in the crash event, and the crash stack description information includes at least one crash stack description item;
the target crash stack description item extracting module is used for extracting at least one target crash stack description item associated with the service code from the crash stack description information;
and the crash statistics module is used for carrying out crash statistics on the application program according to each target crash stack description item.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the crash statistics method for the application provided by any of the embodiments of the invention.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the crash statistics method for an application program provided in any embodiment of the present invention.
The technical scheme of the embodiment of the invention extracts the target collapse stack description item associated with the service code from the collapse stack description item of the collapse stack description information to carry out collapse statistics by acquiring the collapse event of the application program reported by the client and extracting the collapse stack description information in the collapse event. The method and the device solve the problems that in the prior art, the breakdown can only be reflected by the breakdown attribute in a classification and statistics mode according to the bottom reason, and abnormal service codes cannot be positioned, realize the breakdown statistics of the application program based on the stack information, and more intuitively reflect the breakdown occurrence reason, thereby improving the application program repairing efficiency.
Drawings
FIG. 1a is a flowchart of a crash statistics method for an application according to a first embodiment of the present invention;
FIG. 1b is a diagram of crash stack description information and crash stack description entries suitable for use in embodiments of the present invention;
FIG. 2a is a flowchart of a crash statistics method for an application according to a second embodiment of the present invention;
FIG. 2b is a schematic diagram of a library name suitable for use in embodiments of the present invention;
FIG. 2c is a diagram of a crash statistics suitable for use in embodiments of the present invention;
FIG. 3 is a schematic structural diagram of a crash statistics apparatus for an application according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device in a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Example one
Fig. 1a is a flowchart of an application crash statistics method in an embodiment of the present invention, where this embodiment is applicable to a situation of performing crash statistics on an application in a client, and the method may be executed by an application crash statistics apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in a terminal device or a server.
As shown in fig. 1a, the method comprises:
s110, a crash event of the application program reported by the client is obtained, and crash stack description information included in the crash event is extracted, wherein the crash stack description information includes at least one crash stack description item.
The crash refers to stopping or disappearing of the process of the application program, and the crash has many reasons, such as function stack overflow, array out-of-bounds access or unavailability of a target object of a pointer, and the like. The crash stack description information refers to stack information collected by the client when the application program crashes, that is, information related to the called condition of the function of the application program when the application program crashes. FIG. 1b provides a schematic diagram of crash stack description information and crash stack description entries, where the information in the box of FIG. 1b is the crash stack description information. The crash stack description information includes a plurality of crash stack description entries, and 0-4 rows in the box of FIG. 1b, where each row corresponds to a crash stack description entry.
When the application program is crashed, the client collects the crash stack description information, generates a crash event according to the crash stack description information, and reports the crash event to the server.
Optionally, the crash stack description item may include: the library name, class name, and method name corresponding to the crash code.
The crash code refers to source code related to the crash of the application process, the crash code includes service code and system code, the service code refers to code written by a developer and directly used for realizing a certain requirement, and the system code refers to code which can exist without the service.
The library name refers to the name of the function library, and is, for example, "libhymedia libraries" in fig. 1 b. The class name refers to a name that references a data type, and exemplarily, "timezone" in fig. 1b is a class name. The method name is the name of the called method, and for example, "IoEngine" in FIG. 1b is a method name.
S120, extracting at least one target crash stack description item associated with the service code from the crash stack description information.
And extracting only the crash stack description item associated with the business code as a target crash stack description item from the crash stack description items in the crash stack description information.
In the embodiment of the invention, the service code is a code written by a developer, only the crash stack description item related to the service code is extracted for performing crash statistics, the crash stack description item related to the system code is effectively eliminated, the classification of the crash problem based on the service code can be realized, the developer can directly position the specific reason of the crash occurrence, and the repair efficiency of the application crash is improved on a certain level.
S130, performing crash statistics on the application program according to the target crash stack description items.
According to each crash stack description item associated with the service code, performing crash statistics on the application program, classifying crash events of the application programs with the same target crash stack description item into one class, and classifying the crash events according to wrong service codes, namely classifying and counting the crash events according to the specific reasons of the crash occurrence. By the aid of the method, developers can perform fault troubleshooting by focusing on actual wrong service codes when fault analysis is performed by taking the breakdown statistical result as a data basis, and accordingly the application breakdown repairing efficiency is improved.
According to the technical scheme of the embodiment of the invention, the collapse statistics is carried out by acquiring the collapse event of the application program reported by the client, extracting the collapse stack description information in the collapse event, and extracting the target collapse stack description item associated with the service code from the collapse stack description item of the collapse stack description information. The method and the device solve the problems that in the prior art, the breakdown can only be reflected by the breakdown attribute in a classification and statistics mode according to the bottom reason, and abnormal service codes cannot be positioned, realize the breakdown statistics of the application program based on the stack information, and more intuitively reflect the breakdown occurrence reason, thereby improving the application program repairing efficiency.
Optionally, the statistical method for the crash of the application program may further include: in response to a crash query request to the application program, obtaining at least one query crash classification that matches the crash query request; and taking each query crash classification and a crash statistic value respectively corresponding to each query crash classification as a feedback result of the crash query request.
The crash query request is a request for querying a crash category, the crash category corresponds to the target crash stack description item, and the target crash stack description item is different among different crash categories. After performing crash classification based on the target crash stack description item and performing crash statistics on each crash event of the application program to obtain a crash statistical result, the embodiment of the invention further provides a crash query function based on the crash statistical result, so that different crash classifications and crash statistical values corresponding to each crash classification can be visually displayed.
The query crash classification is a crash classification that the user wants to query, and a crash query request may correspond to one or more query crash classifications. According to the crash query request, the query crash classification and the crash statistics corresponding to the query crash classification can be obtained in the crash classification of the crash statistics result, and the query crash classification and the crash statistics corresponding to the query crash classification are fed back to the user.
Example two
Fig. 2a is a flowchart of a crash statistics method for an application program in the second embodiment of the present invention, and in this embodiment, based on the above embodiments, a process of extracting a target crash stack description item and a process of performing crash statistics according to the target crash stack description item are further refined, and a step of performing crash classification query is added.
Correspondingly, the method of the embodiment may include:
s210, a crash event of the application program reported by the client is obtained, and crash stack description information included in the crash event is extracted, wherein the crash stack description information includes at least one crash stack description item.
S220, obtaining library names corresponding to the crash stack description items in the crash stack description information.
In the embodiment of the invention, each crash stack description item in the crash stack description information is extracted, and the library name corresponding to each crash stack description item is obtained. For example, fig. 2b provides a schematic diagram of a library name, and the "libc.
And S230, matching each extracted library name with a standard service code library name set to obtain at least one target library name successfully matched.
The server stores standard service code library name set for recording library names associated with service codes written by developers. In each library name, the library name existing in the standard service code library name set is obtained as a target library name, and the collapse stack description information corresponding to the target library name is the stack information corresponding to the wrong service code.
For example, as shown in fig. 2b, there is "libhymedia catarars.so" in the standard service code library name set, so that the "libhymedia catarars.so" in the 3-4 rows is the target library name.
S240, determining the crash stack description item corresponding to the target library name as a target crash stack description item associated with the service code.
The crash stack description item corresponding to the target library name is the target crash stack description item associated with the wrong service code, so that the target crash stack description item can be used for representing the specific occurrence reason of the crash, and classification statistics can be performed on the crash based on the target crash stack description item.
For example, when "libhymedia data in fig. 2b is the target library name, the target crash stack description item is the contents of lines 3-4 in fig. 1 b.
And S250, calculating a target signature value corresponding to the crash event according to each target crash stack description item and a preset signature algorithm.
In the embodiment of the invention, the crash event can be signed according to the target crash stack description item, and the target signature value of the crash event is calculated, wherein the target signature value is in one-to-one correspondence with each target crash stack description item. The target signature value is used as an identifier of a specific reason for the crash occurrence, and is a basis for classifying the crash event.
Optionally, a Hash Algorithm may be used as the signature Algorithm, a sha1(Secure Hash Algorithm 1) value corresponding to the target crash stack description item is calculated through the Hash Algorithm, the sha value is used as the target signature value, and an MD5(Message Digest Algorithm, fifth version of Message Digest Algorithm) value may also be calculated through the Hash Algorithm and used as the target signature value, which is not limited in this embodiment.
And S260, judging whether a target crash classification corresponding to the target signature value is stored currently, if so, executing S290, otherwise, executing S270.
In the embodiment of the invention, if the target crash classification corresponding to the target signature value is stored currently, the target crash classification corresponding to the target signature value is indicated as the existing crash classification, and the target crash classification is directly counted. If no target crash classification corresponding to the target signature value exists at present, the target crash classification is a brand new crash classification, and each target crash stack description item can be used as the target crash classification for storage and statistics.
S270, all the target crash stack description items are used as target crash classifications of the application crash events.
In the embodiment of the invention, classification statistics is carried out on the crashes based on the target crash stack description items, so that when no target crash classification exists currently, each target crash stack description item is saved as a target crash classification.
S280, establishing a mapping relation between the target crash classification and the target signature value. S290 is performed.
In the embodiment of the invention, after the mapping relation between the target crash classification and the target signature value is established, when a new crash event occurs, the target signature value corresponding to the new crash event can be calculated, so that the crash event is classified according to the signature value.
S290, updating the crash statistics value corresponding to the target crash classification.
After the target crash classification for the crash event is determined, the crash statistics for the target crash classification can be updated.
Accordingly, S290 may further include the following steps:
and S291, acquiring the target equipment identifier matched with the crash event.
In the embodiment of the present invention, after determining the crash classification corresponding to the crash event, performing crash information statistics to count the device identifier corresponding to the crash event. By the arrangement, developers at the server side can know the devices corresponding to the breakdown classifications according to the breakdown statistical result, so that the developers can perform fault location on the devices with the breakdown events, and the repair efficiency of the breakdown of the application program is improved in another dimension.
S292, judging whether the device identification set corresponding to the target crash classification comprises the target device identification, if so, executing S293, otherwise, executing S294.
The device identification sets store device identifications corresponding to all devices of the type of the crash event that the application program has a target crash classification.
S293, only the number of times of collapse corresponding to the target collapse classification is updated.
The number of times of crash is the number of times of crash events corresponding to the target crash classification, and if the device identifier set includes the target device identifier, it indicates that a crash event of the target crash classification type has occurred before the application program of the current device, and only the number of times of crash of the target crash classification needs to be updated.
S294, adding the target device identifier into the device identifier set, and updating the number of devices and the number of times of collapse corresponding to the target collapse classification.
The device number refers to the number of devices that have a crash event corresponding to the target crash classification, and if the device identifier set does not include the target device identifier, it indicates that a crash event of the target crash classification type has not occurred before the application program of the current device, and the device number and the crash times need to be updated simultaneously.
For example, fig. 2c provides a schematic diagram of a crash statistics result, as shown in fig. 2c, the target crash stack description item is used to represent a target crash classification, the crash statistics value of the target crash classification includes a number of times of crash and a number of devices, and the number of times of crash is generally greater than or equal to the number of devices.
In this embodiment, when updating the crash statistics, the device identifier set corresponding to a certain target crash category is further counted, so that the number of devices corresponding to the target crash category can be updated. Accordingly, when performing subsequent fault location, a troubleshooting person (generally, a programmer of a service code corresponding to the target crash classification) may determine, according to a numerical relationship between the number of devices of the target crash classification or the number of devices and the number of times of crash, whether the target crash classification is a first type of error unrelated to the device (for example, the number of devices exceeds a preset device number threshold), or a second type of error associated with a specific device (for example, the number of times of crash is far greater than the number of devices).
Furthermore, if the target breakdown classification is determined to belong to the second type of error, the common characteristics of the devices in the device identification set can be identified according to the device identification set corresponding to the target breakdown classification, so that troubleshooting personnel can be helped to quickly locate the fault reason, and the code repairing efficiency is improved.
S2100, judging whether a crash query request for the application program is received, if so, executing S2110, otherwise, returning to execute S2100.
The embodiment of the invention also provides a function of crash classification query, and when a user needs to query the crash classification, a crash query request is initiated to the server.
S2110, obtaining at least one query crash classification matched with the crash query request.
The query crash classification is a crash classification that the user wants to query, and the query crash classification can be one or more.
S2120, using each query crash classification and a crash statistic corresponding to each query crash classification as a feedback result of the crash query request.
And obtaining query crash classifications in each crash classification of the crash statistical result, and feeding back each query crash classification and the corresponding equipment number and crash times thereof to the user.
According to the technical scheme of the embodiment of the invention, the crash event of the application program reported by the client is obtained, the crash stack description information in the crash event is extracted, the target crash stack description item associated with the service code is extracted from the crash stack description item of the crash stack description information, the target signature value is calculated according to each target crash stack description item, the target crash classification is determined according to the target signature value, and the crash statistic value of the target crash classification is further updated. The method and the device solve the problems that in the prior art, the breakdown can only be reflected by the breakdown attribute in a classification and statistics mode according to the underlying reason, and abnormal service codes cannot be positioned, realize the breakdown statistics of the application program based on the stack information, more visually reflect the breakdown occurrence reason, position the service codes related to the breakdown event, and position the equipment with the breakdown event, thereby improving the application program repairing efficiency.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a crash statistics apparatus for an application according to a third embodiment of the present invention. As shown in fig. 3, the crash statistics apparatus of the application includes: crash stack description information extraction module 310, target crash stack description item extraction module 320, and crash statistics module 330, wherein:
the crash stack description information extraction module 310 is configured to obtain a crash event of an application program reported by a client, and extract crash stack description information included in the crash event, where the crash stack description information includes at least one crash stack description item;
a target crash stack description item extracting module 320, configured to extract at least one target crash stack description item associated with a service code from the crash stack description information;
the crash statistics module 330 is configured to perform crash statistics on the application program according to each target crash stack description item.
According to the technical scheme of the embodiment of the invention, the collapse statistics is carried out by acquiring the collapse event of the application program reported by the client, extracting the collapse stack description information in the collapse event, and extracting the target collapse stack description item associated with the service code from the collapse stack description item of the collapse stack description information. The method and the device solve the problems that in the prior art, the breakdown can only be reflected by the breakdown attribute in a classification and statistics mode according to the bottom reason, and abnormal service codes cannot be positioned, realize the breakdown statistics of the application program based on the stack information, and more intuitively reflect the breakdown occurrence reason, thereby improving the application program repairing efficiency.
On the basis of the above embodiment, the crash stack description item includes: the library name, class name, and method name corresponding to the crash code.
On the basis of the above embodiment, the target crash stack description item extracting module 320 includes:
a library name obtaining unit, configured to obtain, in the collapse stack description information, a library name corresponding to each collapse stack description item;
the target library name acquisition unit is used for matching each extracted library name with a standard service code library name set to acquire at least one target library name which is successfully matched;
and the target crash stack description item determining unit is used for determining the crash stack description item corresponding to the target library name as the target crash stack description item associated with the service code.
On the basis of the foregoing embodiment, the crash statistics module 330 includes:
the target signature value calculating unit is used for calculating a target signature value corresponding to the crash event according to each target crash stack description item and a preset signature algorithm;
and the crash statistic updating unit is used for updating the crash statistic corresponding to the target crash classification if the target crash classification corresponding to the target signature value is currently stored, wherein the crash classification comprises at least one crash stack description item.
On the basis of the above embodiment, the apparatus further includes:
a target crash classification determination module, configured to, if a target crash classification corresponding to the target signature value is not currently stored, use all target crash stack description items as a target crash classification of the application crash event;
and the crash statistic updating module is used for establishing a mapping relation between the target crash classification and the target signature value and updating the crash statistic corresponding to the target crash classification.
On the basis of the foregoing embodiment, the crash statistics updating unit and the crash statistics updating module are specifically configured to:
acquiring a target device identifier matched with the crash event;
if the device identification set corresponding to the target crash classification comprises the target device identification, only updating the crash times corresponding to the target crash classification;
and if the device identifier set corresponding to the target crash classification does not comprise the target device identifier, adding the target device identifier into the device identifier set, and updating the device number and the crash times corresponding to the target crash classification.
On the basis of the above embodiment, the apparatus further includes:
the query crash classification acquisition module is used for responding to a crash query request of the application program and acquiring at least one query crash classification matched with the crash query request;
and the feedback result acquisition module is used for taking each query crash classification and a crash statistic value respectively corresponding to each query crash classification as a feedback result of the crash query request.
The application program crash statistical device provided by the embodiment of the invention can execute the application program crash statistical method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Example four
Fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. Fig. 4 illustrates a block diagram of an exemplary device 12 suitable for use in implementing embodiments of the present invention. The device 12 shown in fig. 4 is only an example and should not bring any limitation to the function and scope of use of the embodiments of the present invention.
As shown in FIG. 4, device 12 is in the form of a general purpose computing device. The components of device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. Device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing a crash statistics method for application programs provided by embodiments of the present invention. Namely: the method for realizing the crash statistics of the application program comprises the following steps:
acquiring a crash event of an application program reported by a client, and extracting crash stack description information included in the crash event, wherein the crash stack description information includes at least one crash stack description item;
extracting at least one target crash stack description item associated with a service code from the crash stack description information;
and performing crash statistics on the application program according to each target crash stack description item.
EXAMPLE five
The fifth embodiment of the present invention further discloses a computer storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the method for performing crash statistics on an application program includes:
acquiring a crash event of an application program reported by a client, and extracting crash stack description information included in the crash event, wherein the crash stack description information includes at least one crash stack description item;
extracting at least one target crash stack description item associated with a service code from the crash stack description information;
and performing crash statistics on the application program according to each target crash stack description item.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer-readable storage medium may be, for example, but is not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments illustrated herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A method for application crash statistics, comprising:
acquiring a crash event of an application program reported by a client, and extracting crash stack description information included in the crash event, wherein the crash stack description information includes at least one crash stack description item;
extracting at least one target crash stack description item associated with a service code from the crash stack description information;
and performing crash statistics on the application program according to each target crash stack description item.
2. The method of claim 1, wherein the crashing stack description entry comprises: the library name, class name, and method name corresponding to the crash code.
3. The method of claim 2, wherein extracting at least one target crash stack description item associated with a business code in the crash stack description information comprises:
in the collapse stack description information, obtaining library names corresponding to the collapse stack description items respectively;
matching each extracted library name with a standard service code library name set to obtain at least one target library name which is successfully matched;
and determining the crash stack description item corresponding to the target library name as a target crash stack description item associated with the service code.
4. The method of claim 1, wherein performing crash statistics on the application based on each of the target crash stack description entries comprises:
calculating a target signature value corresponding to the crash event according to each target crash stack description item and a preset signature algorithm;
and if the target crash classification corresponding to the target signature value is stored currently, updating a crash statistic value corresponding to the target crash classification, wherein the crash classification comprises at least one crash stack description item.
5. The method of claim 4, further comprising, after computing a target signature value corresponding to the crash event:
if the target crash classification corresponding to the target signature value is not stored currently, all target crash stack description items are used as the target crash classification of the application crash event;
and establishing a mapping relation between the target crash classification and the target signature value, and updating a crash statistic value corresponding to the target crash classification.
6. The method of claim 4 or 5, wherein updating crash statistics associated with the target crash classification comprises:
acquiring a target device identifier matched with the crash event;
if the device identification set corresponding to the target crash classification comprises the target device identification, only updating the crash times corresponding to the target crash classification;
and if the device identifier set corresponding to the target crash classification does not comprise the target device identifier, adding the target device identifier into the device identifier set, and updating the device number and the crash times corresponding to the target crash classification.
7. The method of any one of claims 1-5, further comprising:
in response to a crash query request to the application program, obtaining at least one query crash classification that matches the crash query request;
and taking each query crash classification and a crash statistic value respectively corresponding to each query crash classification as a feedback result of the crash query request.
8. An apparatus for application crash statistics, comprising:
the system comprises a crash stack description information extraction module, a crash stack description information extraction module and a data processing module, wherein the crash stack description information extraction module is used for acquiring a crash event of an application program reported by a client and extracting crash stack description information included in the crash event, and the crash stack description information includes at least one crash stack description item;
the target crash stack description item extracting module is used for extracting at least one target crash stack description item associated with the service code from the crash stack description information;
and the crash statistics module is used for carrying out crash statistics on the application program according to each target crash stack description item.
9. An electronic device comprising one or more processors; storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the crash statistics method for the application program as recited in any one of claims 1-7.
10. A storage medium containing computer-executable instructions, which when executed by a computer processor, are operable to perform a crash statistics method for an application program as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011173313.9A CN112306833A (en) | 2020-10-28 | 2020-10-28 | Application program crash statistical method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011173313.9A CN112306833A (en) | 2020-10-28 | 2020-10-28 | Application program crash statistical method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112306833A true CN112306833A (en) | 2021-02-02 |
Family
ID=74331426
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011173313.9A Pending CN112306833A (en) | 2020-10-28 | 2020-10-28 | Application program crash statistical method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306833A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113591980A (en) * | 2021-07-30 | 2021-11-02 | 上海识装信息科技有限公司 | Application program crash stack assignment method, device and storage medium |
| CN113867847A (en) * | 2021-11-30 | 2021-12-31 | 统信软件技术有限公司 | Abnormal plug-in processing method and device and computing equipment |
| CN116991505A (en) * | 2023-09-26 | 2023-11-03 | 统信软件技术有限公司 | Plug-in loading method, device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030084376A1 (en) * | 2001-10-25 | 2003-05-01 | Nash James W. | Software crash event analysis method and system |
| CN110489345A (en) * | 2019-08-08 | 2019-11-22 | 北京字节跳动网络技术有限公司 | A kind of collapse polymerization, device, medium and equipment |
| CN110647472A (en) * | 2019-09-27 | 2020-01-03 | 北京博睿宏远数据科技股份有限公司 | Breakdown information statistical method and device, computer equipment and storage medium |
| CN110727581A (en) * | 2019-09-06 | 2020-01-24 | 网宿科技股份有限公司 | Collapse positioning method and electronic equipment |
| CN110865898A (en) * | 2019-10-12 | 2020-03-06 | 北京字节跳动网络技术有限公司 | Method, device, medium and equipment for clustering crash call stack |
-
2020
- 2020-10-28 CN CN202011173313.9A patent/CN112306833A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030084376A1 (en) * | 2001-10-25 | 2003-05-01 | Nash James W. | Software crash event analysis method and system |
| CN110489345A (en) * | 2019-08-08 | 2019-11-22 | 北京字节跳动网络技术有限公司 | A kind of collapse polymerization, device, medium and equipment |
| CN110727581A (en) * | 2019-09-06 | 2020-01-24 | 网宿科技股份有限公司 | Collapse positioning method and electronic equipment |
| CN110647472A (en) * | 2019-09-27 | 2020-01-03 | 北京博睿宏远数据科技股份有限公司 | Breakdown information statistical method and device, computer equipment and storage medium |
| CN110865898A (en) * | 2019-10-12 | 2020-03-06 | 北京字节跳动网络技术有限公司 | Method, device, medium and equipment for clustering crash call stack |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113591980A (en) * | 2021-07-30 | 2021-11-02 | 上海识装信息科技有限公司 | Application program crash stack assignment method, device and storage medium |
| CN113867847A (en) * | 2021-11-30 | 2021-12-31 | 统信软件技术有限公司 | Abnormal plug-in processing method and device and computing equipment |
| CN116991505A (en) * | 2023-09-26 | 2023-11-03 | 统信软件技术有限公司 | Plug-in loading method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109284269B (en) | Abnormal log analysis method and device, storage medium and server | |
| CN112306833A (en) | Application program crash statistical method and device, computer equipment and storage medium | |
| CN107819627B (en) | System fault processing method and server | |
| US20200012550A1 (en) | Enabling symptom verification | |
| CN110647472A (en) | Breakdown information statistical method and device, computer equipment and storage medium | |
| CN110825694A (en) | Data processing method, device, equipment and storage medium | |
| CN113238815B (en) | Interface access control method, device, equipment and storage medium | |
| CN109408361A (en) | Monkey tests restored method, device, electronic equipment and computer readable storage medium | |
| CN112130781A (en) | Log printing method and device, electronic equipment and storage medium | |
| CN111782431A (en) | Exception processing method, exception processing device, terminal and storage medium | |
| CN108111328B (en) | Exception handling method and device | |
| CN110717130B (en) | Dotting method, dotting device, dotting terminal and storage medium | |
| CN111046393B (en) | Vulnerability information uploading method and device, terminal equipment and storage medium | |
| CN112506490A (en) | Interface generation method and device, electronic equipment and storage medium | |
| JP7235110B2 (en) | Operation log acquisition device, operation log acquisition method, and operation log acquisition program | |
| CN117033058A (en) | Analysis method, device, equipment and medium for software crash data | |
| CN115022201B (en) | Data processing function test method, device, equipment and storage medium | |
| CN111741046B (en) | Data reporting method, data acquisition method, device, equipment and medium | |
| US20230409468A1 (en) | Providing application error data for use by third-party library development systems | |
| CN111061744B (en) | Graph data updating method and device, computer equipment and storage medium | |
| CN112131611A (en) | Data correctness verification method, device, equipment, system and storage medium | |
| CN112162954A (en) | User operation log generation method, user operation log generation device | |
| CN113377604A (en) | Data processing method, device, equipment and storage medium | |
| CN112306819B (en) | Abnormal event playback method and device, electronic equipment and storage medium | |
| CN116909838B (en) | Abnormal log reporting method, system, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210202 |
|
| RJ01 | Rejection of invention patent application after publication |