CN113835912B - Crash information processing method and device for application program - Google Patents
Crash information processing method and device for application program Download PDFInfo
- Publication number
- CN113835912B CN113835912B CN202010584333.9A CN202010584333A CN113835912B CN 113835912 B CN113835912 B CN 113835912B CN 202010584333 A CN202010584333 A CN 202010584333A CN 113835912 B CN113835912 B CN 113835912B
- Authority
- CN
- China
- Prior art keywords
- information
- specific information
- application program
- network request
- crash
- 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.)
- Active
Links
- 230000010365 information processing Effects 0.000 title claims description 11
- 238000003672 processing method Methods 0.000 title claims description 10
- 238000000034 method Methods 0.000 claims abstract description 37
- 230000002159 abnormal effect Effects 0.000 claims abstract description 14
- 230000005540 biological transmission Effects 0.000 claims description 8
- 230000015556 catabolic process Effects 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 9
- 230000002085 persistent effect Effects 0.000 description 6
- 230000008439 repair process Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 230000008030 elimination Effects 0.000 description 2
- 238000003379 elimination reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000002355 dual-layer Substances 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Retry When Errors Occur (AREA)
Abstract
The application relates to a method and equipment for processing crash information of an application program, wherein the method comprises the following steps: judging whether the last closing of the application program is abnormal closing or not; if yes, the crash information of the application program is sent to a server, wherein the crash information comprises a crash stack file and specific information of the latest N network requests which are stored; where N is a predetermined positive integer. The scheme provided by the application program crash method and the application program crash system enable the server side to quickly determine the crash reasons of the application program.
Description
Technical Field
The present invention relates to the field of software technologies, and in particular, to a method and an apparatus for processing crash information of an application program.
Background
Along with social development and progress of software technology, application programs on the intelligent terminal are also layered endlessly, after a user starts an Application program (APP) of the intelligent terminal, APP crashes possibly due to various reasons, and relevant information of the Application program crashes is collected, so that a technician can be helped to locate a specific reason of the Application program crashes.
More common causes of breakdown on APP lines may be: the device fragmentation, bandwidth limitation, network change, excessive users, code errors, back-end data problems, memory overflow, no corresponding method found and other types are adopted, and the reason for breakdown is difficult to accurately judge because the use environments of online users are different, so that a great deal of manpower and time are required.
Disclosure of Invention
In order to overcome the problems in the related art, the application program crash information and equipment are provided, and the application program crash information processing method and equipment can quickly determine the cause of the crash of the application program.
The first aspect of the present application provides a crash information processing method for an application program, including:
judging whether the last closing of the application program is abnormal closing or not;
if yes, the crash information of the application program is sent to a server, wherein the crash information comprises a crash stack file and specific information of the latest N network requests which are stored; where N is a predetermined positive integer.
A second aspect of the present application provides an intelligent terminal, including:
the judging unit is used for judging whether the last closing of the application program is abnormal closing or not;
the sending unit is used for sending the crash information of the application program to a server when the judging result of the judging unit is yes, wherein the crash information comprises a crash stack file and specific information of the latest N network requests which are stored; where N is a predetermined positive integer.
A third aspect of the present application provides an electronic device, comprising:
a processor; and
a memory having executable code stored thereon which, when executed by the processor, causes the processor to perform the method as described above.
A fourth aspect of the present application provides a non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method as described above.
The technical scheme that this application provided can include following beneficial effect: in the embodiment of the application, when the application program has a crash error, the terminal uploads the crash stack information and the latest N network requests to the server after restarting, and a technician at the server end restores the network environment when the application crashes through the crash information, so that the cause of the crash is quickly determined.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The foregoing and other objects, features and advantages of the application will be apparent from the following more particular descriptions of exemplary embodiments of the application as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts throughout the exemplary embodiments of the application.
FIG. 1 is a first flow chart of a crash information processing method of an application program according to an embodiment of the present disclosure;
FIG. 2 is a second flow diagram of a crash information processing method of an application program according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an intelligent terminal of an application program according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Preferred embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first message may also be referred to as a second message, and similarly, a second message may also be referred to as a first message, without departing from the scope of the present application. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
In the related art, the type of online crash is determined by searching the crash cause of the program mainly based on experience of the programmer, and many crashes are analyzed by the collected crash stack information of the application program and the determination of the programmer because of the reason that the front end and the rear end transmit data (hereinafter collectively referred to as interfaces). However, with the current technical means, only the online application user can check the problem when clicking the commodity list to the commodity details in some cases through the crash stack, the network environment used by the user at the time and the operation condition of the mobile phone cannot be completely restored, and the problem of the back-end data and the memory overflow … … can be sequentially removed step by step only through a removal method, so that the problem can be removed step by step, and a great amount of time can be spent in checking the problem. If a large amount of time is spent to find out that a certain field of the commodity is possibly due to a problem, the commodity is searched again in an elimination method, firstly, a back-end database is firstly searched to find out whether the problem exists when the database is stored, if the problem exists when the database is stored, then, whether the problem exists when an interface is converted is eliminated, because the specific commodity ID cannot be accurately positioned, the elimination work is that the workload of multiple of one hundred million is increased, the real reason of program breakdown is difficult to determine in the related technology, and the consumed labor is extremely large. In view of the above problems, embodiments of the present application provide a method for processing crash information of an application program, which can quickly determine a specific cause of the crash of the application program.
The following describes the technical scheme of the embodiments of the present application in detail with reference to the accompanying drawings.
Fig. 1 is a first flowchart of a crash information processing method of an application program according to an embodiment of the present application.
Referring to fig. 1, a method for processing crash information of an application provided in an embodiment of the present application includes:
s101, judging whether the last closing of the application program is abnormal closing, if so, executing S102, otherwise, executing S103;
in this embodiment, the application program may be, but is not limited to, an application program installed on an intelligent terminal such as a mobile phone, a tablet computer, a personal computer, etc.;
for example, the determination in S101 may be performed when the application program crashes, when the application program is started, or during the running process after the starting;
s102, sending the collapse information of the application program to a server;
if the last closing of the application program is abnormal closing, possibly caused by the crash of the application program, the crash information is sent to the server;
wherein the crash information comprises a crash stack file and specific information of the latest N network requests which are stored;
it should be noted that, in the embodiments of the present application, the "network request" refers to a network request sent by the application program;
wherein N is a predetermined positive integer, for example N is a number of 1, 2, 3, 5, etc.;
preferably, N may be a fixed value set in advance, or may be a value that changes dynamically, for example, may be determined according to the number of network requests sent by the application program within a predetermined time (for example, 1 second or 3 seconds) before the occurrence of a crash, so that the network requests within a certain time before the occurrence of the crash may be uploaded to the server;
s103, executing other operations.
If the last shutdown of the application is a normal shutdown, for example, the application is actively shutdown according to the instruction of the user, the crash information does not need to be uploaded.
After the server acquires the crash information, a technician at the server side can determine whether the crash reason of the application program is related to the network interface data by utilizing the crash stack file and the specific information of the latest N network requests, and if so, determine which network interface data are in error by utilizing the specific information of the latest N network requests, so that the application program crashes.
According to the crash information processing method of the application program, if the application program is crashed, after the application program is started again, the application program can send the crash stack file and the saved specific information of the latest N network requests to the server, and a server side technician can quickly determine the specific reason of the software crash by utilizing the crash stack file and the specific information of the latest N network requests.
FIG. 2 is a second flow chart of a crash information processing method of an application program according to an embodiment of the present application.
Referring to fig. 2, another method for processing crash information of an application provided in an embodiment of the present application includes:
s201, starting an application program;
in this embodiment, the application program may be, but is not limited to, an application program installed on an intelligent terminal such as a mobile phone, a tablet computer, a personal computer, etc.;
s202, judging whether the application program is started for the first time, if so, executing S203, otherwise, executing S204;
s203, creating a target file locally, wherein the target file is used for storing specific information of a network request;
if the application program is started for the first time, a target file is locally created in the intelligent terminal, wherein the target file is used for storing specific information of a network request sent by the intelligent terminal;
s204, judging whether the last closing of the application program is abnormal closing, if so, executing S205, otherwise, executing S206;
after the application program crashes, the application program can be restarted automatically or according to the instruction input by the user;
s205, sending the collapse information of the application program to a server;
if the last closing of the application program is abnormal closing, possibly caused by the crash of the application program, the crash information is sent to the server;
the crash information comprises specific information of the latest N network requests stored in the crash stack file and the target file;
where N is a predetermined positive integer, for example N is a number of 1, 2, 3, 5, etc., preferably N may be 3;
s206, executing other operations.
If the last shutdown of the application is a normal shutdown, for example, the application is actively shutdown according to the instruction of the user, the crash information does not need to be uploaded.
Preferably, the method may further comprise: when the application program sends a network request, specific information of the network request is stored;
specifically, the specific information of the network request may be written into the target file for saving, and each network request may be saved in the target file for standby.
Preferably, in the above-mentioned object file, the specific information of each network request may be arranged into a queue according to the sequence of the sending time of the network requests, so that the specific information of the first N network requests, that is, the specific information of the last N network requests, is extracted from the front end of the queue when the crash information is sent.
Preferably, the storing the specific information of the network request includes: if the number of the specific information of the network requests stored in the target file reaches a first preset threshold value M (where M is greater than a positive integer of N, for example, M may be a number of 10, 20, 50, etc.), deleting at least one (for example, 1, 3, 5) specific information of the network requests with earliest sending time in the queue, and writing the latest specific information of the network requests, so that the latest specific information of the M network requests is always stored in the target file; for example, when m=20, if the specific information of 20 network requests is already stored in the queue and reaches the upper limit, the specific information of the 3 network requests with earliest transmission time in the queue is deleted, so as to write the specific information of the latest network request.
Alternatively, preferably, the storing the specific information of the network request includes: if the number of the specific information of the network request stored in the target file reaches a second preset threshold P (where P is greater than a positive integer of N, for example, P may be a value of 10, 20, 50, etc.), the queue is emptied, and the latest specific information of the network request is written; if the sending density of the network requests is very high, when the number of the specific information of the network requests stored in the target file reaches the second preset threshold P, the queue may be emptied to avoid the influence of storage delay on the running of the application program, for example, when p=50, if 50 pieces of specific information of the network requests are already stored in the queue, and the upper limit is reached, the queue is emptied to write the latest specific information of the network requests.
For example, specific information of the network request may include, but is not limited to: the sending information and the back-end return information of the network request;
wherein the transmission information of the network request includes at least one of the following information: URL (Uniform Resource Locator ) of the network request, transmission time of the network request, page where the network request is located;
the URL contains user information, and the back end of the server can determine user identity information according to the URL; the sending time of the network requests can be used for ordering the network requests in the target file so as to send the latest specific information of N network requests when a crash occurs; the last access page information of the application program is arranged in the collapse stack file, and the information of the page where the network request is located can be compared with the last access page in the collapse stack file and can be used for determining which network request the collapse of the application program is related to;
the back-end return information of the network request includes at least one of the following information: whether the network request is successful, specific information of the success of the network request, and specific information of the failure of the network request;
the server acquires the back-end return information of the network request, can determine which network requests fail by using the specific information of success or failure of the network request, and determines which field in the data with errors has errors.
It should be noted that after the server side obtains the specific information of the crash stack file and the latest N network requests, a technician may analyze the specific information of the crash stack file and the latest N network requests to determine which specific data and fields have errors, or may be configured with related analysis software on the server, to automatically analyze the specific information of the crash stack file and the latest N network requests, and further determine which specific data and fields have errors.
Preferably, the method may further comprise: the server repairs the network interface data with errors;
for example, the server may automatically repair the network interface data that has been in error, or repair the network interface data that has been in error, as instructed by a user (e.g., technician) operating the server.
After determining which network interface data are in error, the server can repair the network interface data in error, and after the application program is restarted, the server cannot crash again due to the same reasons, and the server does not need to issue a new application program version or repair software package to the intelligent terminal, so that the purpose of rapidly solving the online problem is achieved.
The following is an example to illustrate the scheme provided in this embodiment: the user can jump to a detail page of an article through a list click in the application program, and under normal conditions, the detail page of the article can be opened, but when a certain article is opened suddenly, the application program crashes. In the related art, a server can only acquire a crash stack file, and then check the crash reasons one by utilizing the crash stack file, which is very time-consuming and labor-consuming. By applying the scheme provided by the embodiment, the crashed stack file and the latest N network requests can be utilized to quickly find out which commodity ID is specific to the product which is crashed, if the data of the commodity is problematic, the success information or failure information of the network requests can determine which specific field of the commodity data is problematic, and then the field of the commodity which is problematic can be modified at the back end, so that other users or the current user does not crash when opening the commodity again, and the problem of crashing the application program is fundamentally solved.
Corresponding to the embodiment of the application function implementation method, the application further provides an intelligent terminal, electronic equipment and corresponding embodiments.
Fig. 3 is a schematic structural diagram of an intelligent terminal according to an embodiment of the present application.
Referring to fig. 3, the intelligent terminal 300 includes:
a judging unit 310, configured to judge whether the last shutdown of the application is abnormal shutdown;
and a sending unit 320 configured to send crash information of the application program to a server when the determination result of the determining unit 310 is yes.
If the last closing of the application program is abnormal closing, possibly caused by the crash of the application program, the crash information is sent to the server;
preferably, the determining unit 310 may determine, when the application is started, whether the last shutdown of the application is abnormal shutdown, and the application may restart itself or by a user when crashing, and after restarting, may send crash information to the server, so that the server may determine a specific cause of the crash.
Wherein the crash information comprises a crash stack file and specific information of the latest N network requests which are stored; where N is a predetermined positive integer, for example, N is a number of 1, 2, 3, 5, etc.
For example, the intelligent terminal 300 may be a mobile phone, a tablet computer, a Personal Computer (PC), or the like, and the determining unit 310 and the transmitting unit 320 may be implemented by a software system, or may be implemented by a combination of software and hardware or a pure hardware system, which is not limited herein.
Preferably, N may be a fixed value (preferably but not limited to set to 3) or a dynamically changing value, for example, may be determined according to the number of network requests sent by the application program within a predetermined time (for example, 1 second or 3 seconds) before the crash occurs, so that the network requests within a certain time before the crash occurs can be uploaded to the server;
after the server acquires the crash information, the crash stack file can be used for determining whether the crash reason of the application program is related to the network interface data, and if so, the specific information of the latest N network requests uploaded by the terminal can be used for determining which network interface data have errors, so that the application program crashes.
Preferably, the intelligent terminal 300 may further include: and the file creation unit is used for creating a target file locally at the intelligent terminal when the application program is started for the first time, wherein the target file is used for storing specific information of a network request sent by the intelligent terminal.
Preferably, the intelligent terminal 300 may further include: the storage unit is used for storing specific information of the network request when the application program sends the network request;
specifically, the specific information of the network request may be written into the target file for saving, and each network request may be saved in the target file for standby.
Preferably, in the above target file, the specific information of each network request may be ordered according to the sequence of the sending time of the network request, so as to extract the first N pieces.
Preferably, in the above-mentioned object file, the specific information of each network request may be arranged into a queue according to the sequence of the sending time of the network requests, so that the specific information of the first N network requests, that is, the specific information of the last N network requests, is extracted from the front end of the queue when the crash information is sent.
Preferably, the above memory unit may be specifically used for: if the number of the specific information of the network requests stored in the target file reaches a first predetermined threshold M (where M is greater than a positive integer of N, for example, M may be a number of 10, 20, etc.), deleting at least one (for example, 1, 3, 5) specific information of the network requests with earliest transmission time in the queue, and writing the latest specific information of the network requests, so that the latest specific information of the M network requests is always stored in the target file.
Alternatively, preferably, the above memory unit may be specifically used for: if the number of the specific information of the network request stored in the target file reaches a second preset threshold value P (where P is greater than a positive integer of N, for example, P may be a numerical value of 10, 20, etc.), the queue is emptied, and the latest specific information of the network request is written; if the sending density of the network requests is high, the queue can be emptied when the quantity of the specific information of the network requests stored in the target file reaches a second preset threshold value P, so that storage delay is avoided.
For example, specific information of the network request may include, but is not limited to: the sending information and the back-end return information of the network request;
wherein the transmission information of the network request includes at least one of the following information: URL (Uniform Resource Locator ) of the network request, transmission time of the network request, page where the network request is located;
the back-end return information of the network request includes at least one of the following information: whether the network request is successful, specific information of the success of the network request, and specific information of the failure of the network request.
The application further provides a crash information processing system of an application program, which includes the intelligent terminal 300 and the server described above, and the intelligent terminal 300 and the server have been described in detail in the foregoing embodiments, and are not described herein again.
The specific manner in which the various units perform the operations in relation to the apparatus and systems of the above embodiments have been described in detail in relation to the embodiments of the method and will not be described in detail here.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Referring to fig. 4, an electronic device 400 includes a memory 410 and a processor 420.
The processor 420 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Memory 410 may include various types of storage units, such as system memory, read Only Memory (ROM), and persistent storage. Where the ROM may store static data or instructions that are required by the processor 420 or other modules of the computer. The persistent storage may be a readable and writable storage. The persistent storage may be a non-volatile memory device that does not lose stored instructions and data even after the computer is powered down. In some embodiments, the persistent storage device employs a mass storage device (e.g., magnetic or optical disk, flash memory) as the persistent storage device. In other embodiments, the persistent storage may be a removable storage device (e.g., diskette, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as dynamic random access memory. The system memory may store instructions and data that are required by some or all of the processors at runtime. Furthermore, memory 410 may include any combination of computer-readable storage media including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), magnetic disks, and/or optical disks may also be employed. In some implementations, memory 1010 may include readable and/or writable removable storage devices such as Compact Discs (CDs), digital versatile discs (e.g., DVD-ROMs, dual-layer DVD-ROMs), blu-ray discs read only, super-density discs, flash memory cards (e.g., SD cards, min SD cards, micro-SD cards, etc.), magnetic floppy disks, and the like. The computer readable storage medium does not contain a carrier wave or an instantaneous electronic signal transmitted by wireless or wired transmission.
The memory 410 has stored thereon executable code that, when processed by the processor 420, can cause the processor 420 to perform some or all of the methods described above.
For example, the electronic device 400 may be a smart terminal, or a server.
The aspects of the present application have been described in detail hereinabove with reference to the accompanying drawings. In the foregoing embodiments, the descriptions of the embodiments are focused on, and for those portions of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments. Those skilled in the art will also appreciate that the acts and modules referred to in the specification are not necessarily required in the present application. In addition, it can be understood that the steps in the method of the embodiment of the present application may be sequentially adjusted, combined and pruned according to actual needs, and the modules in the apparatus of the embodiment of the present application may be combined, divided and pruned according to actual needs.
Furthermore, the method according to the present application may also be implemented as a computer program or computer program product comprising computer program code instructions for performing part or all of the steps of the above-described method of the present application.
Alternatively, the present application may also be embodied as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having stored thereon executable code (or a computer program, or computer instruction code) that, when executed by a processor of an electronic device (or electronic device, server, etc.), causes the processor to perform some or all of the steps of the above-described methods according to the present application.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the application herein may be implemented as electronic hardware, computer software, or combinations of both.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The embodiments of the present application have been described above, the foregoing description is exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the improvement of technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (12)
1. A crash information processing method for an application program, the method comprising:
judging whether the closing of the application program is abnormal closing or not;
if yes, the crash information of the application program is sent to a server, wherein the crash information comprises a crash stack file and specific information of the latest N network requests which are stored; wherein N is a predetermined positive integer; the collapse stack file contains the last access page information of the application program; the specific information of the page where the network request is located can be compared with the last access page information to obtain the network request related to the breakdown of the application program, so that the server automatically analyzes the breakdown stack file and the specific information of the latest N network requests based on deployed analysis software, and therefore error specific data and fields are determined, and the specific information of the network request at least comprises URL (uniform resource locator) containing user information.
2. The method according to claim 1, wherein the method further comprises:
when the application program sends a network request, specific information of the network request is saved.
3. The method according to claim 2, wherein the method further comprises:
when the application program is started for the first time, a target file is created locally, wherein the target file is used for storing specific information of a network request;
the step of saving the specific information of the network request comprises the following steps: and writing the specific information of the network request into the target file.
4. A method according to claim 3, characterized in that the method further comprises:
and arranging the specific information of the plurality of network requests into a queue according to the sequence of the sending time of each network request, and storing the specific information in the target file.
5. The method of claim 4, wherein the storing the specific information of the network request comprises:
and if the number of the specific information of the network requests stored in the target file reaches a first preset threshold, deleting the specific information of at least one network request with the earliest sending time in the queue, and writing the specific information of the latest network request.
6. The method of claim 4, wherein the storing the specific information of the network request comprises:
and if the number of the specific information of the network request stored in the target file reaches a second preset threshold, the queue is emptied, and the latest specific information of the network request is written.
7. The method of claim 1, wherein the specific information requested by the network comprises: and the network requests send information and back-end return information.
8. The method of claim 7, wherein the network requested transmission information includes at least one of the following information: the URL of the network request, the sending time of the network request and the page where the network request is located;
the back-end return information of the network request includes at least one of the following information: whether the network request is successful, specific information of the network request success, and specific information of the network request failure.
9. The method of any of claims 1-8, wherein the determining whether the closing of the application is an abnormal closing comprises:
when the application program is started, whether the closing of the application program is abnormal closing or not is judged.
10. An intelligent terminal, characterized in that the terminal comprises:
the judging unit is used for judging whether the last closing of the application program is abnormal closing or not;
the sending unit is used for sending the crash information of the application program to a server when the judging result of the judging unit is yes, wherein the crash information comprises a crash stack file and specific information of the latest N network requests which are stored; wherein N is a predetermined positive integer; the collapse stack file contains the last access page information of the application program; the specific information of the page where the network request is located can be compared with the last access page information to obtain the network request related to the breakdown of the application program, so that the server automatically analyzes the breakdown stack file and the specific information of the latest N network requests based on deployed analysis software, and therefore error specific data and fields are determined, and the specific information of the network request at least comprises URL (uniform resource locator) containing user information.
11. An electronic device, comprising:
a processor; and
a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method of any of claims 1-9.
12. A non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method of any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010584333.9A CN113835912B (en) | 2020-06-24 | 2020-06-24 | Crash information processing method and device for application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010584333.9A CN113835912B (en) | 2020-06-24 | 2020-06-24 | Crash information processing method and device for application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113835912A CN113835912A (en) | 2021-12-24 |
| CN113835912B true CN113835912B (en) | 2024-02-09 |
Family
ID=78964305
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010584333.9A Active CN113835912B (en) | 2020-06-24 | 2020-06-24 | Crash information processing method and device for application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113835912B (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6330689B1 (en) * | 1998-04-23 | 2001-12-11 | Microsoft Corporation | Server architecture with detection and recovery of failed out-of-process application |
| CN102763368A (en) * | 2009-12-23 | 2012-10-31 | 思杰系统有限公司 | Methods and systems for cross site forgery protection |
| CN104346267A (en) * | 2013-08-08 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and device for generating program bug positioning information |
| CN105320572A (en) * | 2014-06-27 | 2016-02-10 | 腾讯科技（深圳）有限公司 | Browser abnormity processing method, device and system |
| CN106339273A (en) * | 2015-07-14 | 2017-01-18 | 阿里巴巴集团控股有限公司 | Application program restoration method, terminal and server |
| CN107622000A (en) * | 2017-09-19 | 2018-01-23 | 北京京东尚科信息技术有限公司 | A kind of collection of application crash information and report method, device |
| CN107644075A (en) * | 2017-09-19 | 2018-01-30 | 北京京东尚科信息技术有限公司 | The method and apparatus for collecting page info |
| CN108848000A (en) * | 2018-05-07 | 2018-11-20 | 深圳壹账通智能科技有限公司 | Network request test method, device, computer equipment and storage medium |
| CN109445973A (en) * | 2018-09-26 | 2019-03-08 | 中国平安人寿保险股份有限公司 | Position the method and device of application crash |
| CN109542689A (en) * | 2018-11-30 | 2019-03-29 | 努比亚技术有限公司 | Applied program processing method, terminal and computer readable storage medium |
| CN110069403A (en) * | 2019-03-21 | 2019-07-30 | 深圳壹账通智能科技有限公司 | Position method and device, the storage medium, electronic device of crash event |
| CN110502440A (en) * | 2019-08-09 | 2019-11-26 | 北京达佳互联信息技术有限公司 | Debug acquisition methods, device, electronic equipment and the storage medium of location information |
| CN110874298A (en) * | 2019-11-13 | 2020-03-10 | 北京齐尔布莱特科技有限公司 | Request data storage method and terminal equipment |
| CN111258803A (en) * | 2020-02-12 | 2020-06-09 | 北京字节跳动网络技术有限公司 | Collapse positioning method and device and electronic equipment |
| CN111274060A (en) * | 2020-02-10 | 2020-06-12 | 广州虎牙科技有限公司 | Method, device, equipment and storage medium for determining memory abnormity |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9262250B2 (en) * | 2011-12-12 | 2016-02-16 | Crashlytics, Inc. | System and method for data collection and analysis of information relating to mobile applications |
-
2020
- 2020-06-24 CN CN202010584333.9A patent/CN113835912B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6330689B1 (en) * | 1998-04-23 | 2001-12-11 | Microsoft Corporation | Server architecture with detection and recovery of failed out-of-process application |
| CN102763368A (en) * | 2009-12-23 | 2012-10-31 | 思杰系统有限公司 | Methods and systems for cross site forgery protection |
| CN104346267A (en) * | 2013-08-08 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Method and device for generating program bug positioning information |
| CN105320572A (en) * | 2014-06-27 | 2016-02-10 | 腾讯科技（深圳）有限公司 | Browser abnormity processing method, device and system |
| CN106339273A (en) * | 2015-07-14 | 2017-01-18 | 阿里巴巴集团控股有限公司 | Application program restoration method, terminal and server |
| CN107644075A (en) * | 2017-09-19 | 2018-01-30 | 北京京东尚科信息技术有限公司 | The method and apparatus for collecting page info |
| CN107622000A (en) * | 2017-09-19 | 2018-01-23 | 北京京东尚科信息技术有限公司 | A kind of collection of application crash information and report method, device |
| CN108848000A (en) * | 2018-05-07 | 2018-11-20 | 深圳壹账通智能科技有限公司 | Network request test method, device, computer equipment and storage medium |
| CN109445973A (en) * | 2018-09-26 | 2019-03-08 | 中国平安人寿保险股份有限公司 | Position the method and device of application crash |
| CN109542689A (en) * | 2018-11-30 | 2019-03-29 | 努比亚技术有限公司 | Applied program processing method, terminal and computer readable storage medium |
| CN110069403A (en) * | 2019-03-21 | 2019-07-30 | 深圳壹账通智能科技有限公司 | Position method and device, the storage medium, electronic device of crash event |
| CN110502440A (en) * | 2019-08-09 | 2019-11-26 | 北京达佳互联信息技术有限公司 | Debug acquisition methods, device, electronic equipment and the storage medium of location information |
| CN110874298A (en) * | 2019-11-13 | 2020-03-10 | 北京齐尔布莱特科技有限公司 | Request data storage method and terminal equipment |
| CN111274060A (en) * | 2020-02-10 | 2020-06-12 | 广州虎牙科技有限公司 | Method, device, equipment and storage medium for determining memory abnormity |
| CN111258803A (en) * | 2020-02-12 | 2020-06-09 | 北京字节跳动网络技术有限公司 | Collapse positioning method and device and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 运用JAVA异常机制分析安卓应用程序崩溃;龙达鑫;;信息技术与信息化(第04期);160-162 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113835912A (en) | 2021-12-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10379831B2 (en) | Dynamic retrieval of installation packages when installing software | |
| US9268648B1 (en) | System and method for consistency verification of replicated data in a recovery system | |
| CN107391269B (en) | Method and equipment for processing message through persistent queue | |
| CN110650036A (en) | Alarm processing method and device and electronic equipment | |
| US20150193336A1 (en) | Computing device and method for recording system event logs of computing device | |
| CN108475201B (en) | Data acquisition method in virtual machine starting process and cloud computing system | |
| US11789766B2 (en) | System and method of selectively restoring a computer system to an operational state | |
| CN109446455B (en) | Page processing method and device | |
| CN103198122A (en) | Method and device for restarting in-memory database | |
| US10264064B1 (en) | Systems and methods for performing data replication in distributed cluster environments | |
| CN110674008B (en) | Problem disk log information collection method, device, equipment and medium of SSD | |
| CN116501259A (en) | Disk group dual-activity synchronization method and device, computer equipment and storage medium | |
| CN109542341B (en) | Read-write IO monitoring method, device, terminal and computer readable storage medium | |
| CN110910249A (en) | Data processing method and device, node equipment and storage medium | |
| CN111026333A (en) | Access request processing method, processing device, electronic equipment and storage medium | |
| EP3264254B1 (en) | System and method for a simulation of a block storage system on an object storage system | |
| CN113835912B (en) | Crash information processing method and device for application program | |
| US20110202903A1 (en) | Apparatus and method for debugging a shared library | |
| CN110659251A (en) | Data processing method and system and electronic equipment | |
| CN105824622B (en) | Data processing method and electronic equipment | |
| CN103678478A (en) | Information processing apparatus, information processing method, and program | |
| CN116594734A (en) | Container migration method and device, storage medium and electronic equipment | |
| US20230088318A1 (en) | Remotely healing crashed processes | |
| JPWO2020065778A1 (en) | Information processing equipment, control methods, and programs | |
| CN105893394B (en) | Large file simulation method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |