CN113835912A - Application crash information processing method and device - Google Patents
Application crash information processing method and device Download PDFInfo
- Publication number
- CN113835912A CN113835912A CN202010584333.9A CN202010584333A CN113835912A CN 113835912 A CN113835912 A CN 113835912A CN 202010584333 A CN202010584333 A CN 202010584333A CN 113835912 A CN113835912 A CN 113835912A
- Authority
- CN
- China
- Prior art keywords
- information
- specific information
- network request
- crash
- 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.)
- Granted
Links
- 230000010365 information processing Effects 0.000 title description 8
- 238000003672 processing method Methods 0.000 title description 7
- 238000000034 method Methods 0.000 claims abstract description 36
- 230000002159 abnormal effect Effects 0.000 claims abstract description 14
- 230000005540 biological transmission Effects 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 8
- 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 4
- 230000002085 persistent effect Effects 0.000 description 4
- 230000008030 elimination Effects 0.000 description 3
- 238000003379 elimination reaction Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000002355 dual-layer Substances 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 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
- 238000012163 sequencing technique Methods 0.000 description 1
- 230000003068 static effect Effects 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/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; if so, sending crash information of the application program to a server, wherein the crash information comprises a crash stack file and specific information of the stored latest N network requests; wherein N is a predetermined positive integer. According to the scheme provided by the application, the server side can quickly determine the crash reason of the application program.
Description
Technical Field
The present application relates to the field of software technologies, and in particular, to a method and an apparatus for processing crash information of an application.
Background
With social development and progress of software technology, applications on the intelligent terminal are also in a wide range, and after a user starts an Application (APP) of the intelligent terminal, the APP crashes due to various reasons, and relevant information of the crashed Application is collected, so that technicians can be helped to locate specific reasons of the crashed Application.
The more common causes of online breakdowns of APPs may be: the method comprises the following steps of equipment fragmentation, bandwidth limitation, network change, excessive users, code errors, backend data problems, memory overflow, failure to find a corresponding method and the like, and because the use environments of online users are different, the reason of crash is difficult to accurately judge, and a large amount of labor and time are needed.
Disclosure of Invention
In order to solve the problems in the related art, the application provides crash information and equipment of an application program, and the crash information processing method and equipment of the application program can quickly determine the cause of crash of the application program.
A first aspect of the present application provides a method for processing crash information of an application program, including:
judging whether the last closing of the application program is abnormal closing;
if so, sending crash information of the application program to a server, wherein the crash information comprises a crash stack file and specific information of the stored latest N network requests; wherein N is a predetermined positive integer.
The 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;
a sending unit, configured to send crash information of the application program to a server when a determination result of the determining unit is yes, where the crash information includes specific information of a crash stack file and the latest N saved network requests; wherein 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 a method as described above.
The technical scheme provided by the application can comprise the following beneficial effects: 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 being restarted, and a technician at the server end restores the network environment of the application when the application crashes through the crash information to quickly determine the cause of the crash.
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 flowchart of a crash information processing method for an application program according to an embodiment of the present disclosure;
fig. 2 is a second flowchart 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 shown in 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 herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the 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 and 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 to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
In the related art, the finding of the cause of the program crash mainly depends on the experience of the programmer to determine the type of the on-line crash, and it is analyzed through the collected crash stack information of the application program and the determination of the programmer that many crashes are caused by the reason of the front-end and back-end data transmission (hereinafter, collectively referred to as interfaces). However, in the current technical means, only the problem that the online application program user sometimes clicks the commodity list to jump to the commodity details can be checked through the crash stack, the network environment used by the user at that time and the running condition of the mobile phone cannot be completely restored, and only the backend data problem and the memory overflow … … can be sequentially eliminated step by step through the elimination method, so that a great deal of time is spent on eliminating one problem step by step. If it takes a lot of time to find out that a certain field of a commodity is possibly problematic, and the field of the commodity is searched again in the way of elimination, firstly, the back-end database is searched to find out whether the database is problematic when being stored, if the database is not problematic, then whether the database is problematic when the interface is converted is eliminated, because the specific commodity ID cannot be accurately positioned, and the elimination work is increased by the number of hundreds of millions of times, the real reason of program crash is difficult to determine in the related art, and the consumed manpower is very huge. In view of the foregoing problems, embodiments of the present application provide a method for processing crash information of an application program, which can quickly determine a specific reason why the application program crashes.
The technical solutions of the embodiments of the present application are described in detail below 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, and 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, and a personal computer;
for example, the determination in S101 may be performed when the application crashes, when the application is started, or during the running process after the application is started;
s102, sending the crash 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, sending crash information to a server;
wherein the crash information comprises the specific information of the crash stack file and the latest N network requests which are already saved;
it should be noted that, in the embodiments of the present application, "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 preset fixed value, or may be a dynamically changing value, for example, determined according to the number of network requests sent by the application 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 all be uploaded to the server;
s103, executing other operations.
If the last closing of the application program is a normal closing, for example, the closing is actively performed according to the instruction of the user, the crash information does not need to be uploaded.
After the server obtains the crash information, a technician at the server end can determine whether the crash reason of the application program is related to the network interface data by using the crash stack file and the specific information of the latest N network requests, and if so, determine which network interface data are wrong specifically by using the specific information of the latest N network requests, so that the application program is crashed.
In the method for processing crash information of an application program provided in this embodiment, if the application program crashes, after the application program is restarted, the application program will send the specific information of the crash stack file and the latest N network requests that have been stored to the server, and a technician at the server end can quickly determine the specific reason of the software crash by using the specific information of the crash stack file and the latest N network requests.
Fig. 2 is a second flowchart of a crash information processing method for 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 the 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, and a personal computer;
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 the network request;
if the application program is started for the first time, a target file is created locally on the intelligent terminal, and 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 is crashed, the application program can be automatically restarted or restarted according to an instruction input by a user;
s205, sending the crash 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, sending crash information to a server;
the crash information comprises specific information of the crash stack file and the latest N network requests stored in the target file;
wherein N is a predetermined positive integer, for example, N is a number of 1, 2, 3, 5, etc., preferably N may be 3;
s206, other operations are executed.
If the last closing of the application program is a normal closing, for example, the closing is actively performed 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, the specific information of the network request is stored;
specifically, the specific information of the network request may be written into the target file for storage, and each network request may be stored in the target file for standby.
Preferably, in the target file, the specific information of each network request may be arranged into a queue according to the sequence of the transmission time of the network requests, so that the specific information of the first N network requests, that is, the specific information of the most recent N network requests, is extracted from the front end of the queue when the crash information is transmitted.
Preferably, the specific information for storing the network request includes: if the number of pieces of specific information of the network requests stored in the target file reaches a first predetermined 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 piece of specific information of the network request with the earliest sending time (for example, 1, 3, or 5 pieces of specific information) in the queue, and writing the latest piece of specific information of the network request, so that the latest M pieces of specific information of the network request are always stored in the target file; for example, when M is 20, if 20 pieces of network request specific information are already stored in the queue and the upper limit is reached, the 3 pieces of network request specific information with the earliest transmission time in the queue are deleted, so as to write the latest network request specific information.
Alternatively, preferably, the specific information for storing the network request includes: if the number of the specific information of the network request stored in the target file reaches a second predetermined threshold value P (where P is greater than a positive integer of N, for example, P may be a value of 10, 20, 50, etc.), emptying the queue, and writing the latest specific information of the network request; if the transmission density of the network requests is high, and the number of the specific information of the network requests that can be saved in the target file reaches a second predetermined threshold value P, the queue is emptied so as to avoid causing storage delay to affect the application program operation, for example, when P is 50, if 50 pieces of specific information of the network requests are already stored in the queue and an upper limit is reached, the queue is emptied so as to write the specific information of the latest network request.
For example, the specific information requested by the network may include, but is not limited to: sending information of the network request and returning information of the back end;
wherein the sending information of the network request comprises at least one of the following information: URL (Uniform Resource Locator) of the network request, sending time of the network request, and a page where the network request is located;
the URL comprises user information, and the back end of the server can determine the user identity information according to the URL; the sending time of the network requests can be used for sequencing the network requests in the target file so as to send the specific information of the latest N network requests when the crash occurs; the information of the page where the network request is located can be compared with the last access page in the crash stack file, and can be used for determining which network request the crash of the application program is related to;
the back-end return information of the network request comprises at least one of the following information: whether the network request is successful, specific information of success of the network request and specific information of failure of the network request;
the server obtains the back-end return information of the network request, and can determine which network requests fail by using the specific information of success or failure of the network requests, and determine which field of 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 are wrong, or related analysis software is deployed on the server to automatically analyze the specific information of the crash stack file and the latest N network requests, so as to determine which specific data and fields are wrong.
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 the error, or repair the network interface data that has the error according to an instruction input by a user (e.g., a technician) operating the server.
After determining which network interface data are wrong, the server can repair the network interface data with the errors, after the application program is started again, the server does not crash again due to the same reason, and the server does not need to release a new application program version or repair a software package to the intelligent terminal, so that the purpose of rapidly solving the online problem is achieved.
The following examples illustrate the scheme provided in this example: a user can jump to a commodity detail page through a list click in an application program, under a normal condition, the commodity detail page can be opened, but when a certain commodity is opened suddenly, the application program crashes. In the related art, the server can only acquire the crash stack file, and then the crash reason is checked one by using the crash stack file, which is time-consuming and labor-consuming. By applying the scheme provided by the embodiment, the specific commodity ID which generates the crash can be quickly found by using the crash stack file and the latest N network requests, if the data of the commodity has problems, the specific field of the commodity data can be determined to have problems through the success information or the failure information of the network requests, and the field with the problems of the commodity can be modified at the rear end, so that other users or the current user can not crash when opening the commodity again, and the problem that the application program generates the crash is fundamentally solved.
Corresponding to the embodiment of the application function implementation method, the application also provides an intelligent terminal, electronic equipment and a corresponding embodiment.
Fig. 3 is a schematic structural diagram of an intelligent terminal shown in an embodiment of the present application.
Referring to fig. 3, the smart terminal 300 includes:
a determining unit 310, configured to determine whether a last shutdown of the application is an abnormal shutdown;
a sending unit 320, configured to send the crash information of the application to the 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, sending crash information to a server;
preferably, the determining unit 310 may determine whether the last shutdown of the application is an abnormal shutdown when the application is started, and the application may be restarted by itself or by a user when the application crashes, and after the application is restarted, the crash information may be sent to the server, so that the server may determine a specific reason for the crash.
Wherein the crash information comprises the specific information of the crash stack file and the latest N network requests which are already saved; where N is a predetermined positive integer, e.g., 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), and other terminals, and the determining unit 310 and the sending unit 320 may be implemented by a software system, or implemented by a combination of software and hardware system or a pure hardware system, which is not limited herein.
Preferably, N may be a preset fixed value (preferably, but not limited to, set to 3), or may be a dynamically changing value, for example, the N may be determined according to the number of network requests sent by the application within a predetermined time (for example, 1 second or 3 seconds) before the crash occurs, so that the network requests within the predetermined time before the crash occurs may all be uploaded to the server;
after the server obtains the crash information, the server may determine whether the crash reason of the application program is related to the network interface data by using the crash stack file, and if so, may determine which network interface data are in error by using specific information of the latest N network requests uploaded by the terminal, so that the application program is crashed.
Preferably, the smart terminal 300 may further include: and the file creating 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 the specific information of the network request sent by the intelligent terminal.
Preferably, the smart terminal 300 may further include: a storage unit, configured to store 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 storage, and each network request may be stored in the target file for standby.
Preferably, in the target file, the specific information of each network request may be sorted according to the sequence of the sending time of the network request, so as to extract the first N pieces of information.
Preferably, in the target file, the specific information of each network request may be arranged into a queue according to the sequence of the transmission time of the network requests, so that the specific information of the first N network requests, that is, the specific information of the most recent N network requests, is extracted from the front end of the queue when the crash information is transmitted.
Preferably, the storage unit may be specifically configured to: if the number of pieces of 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, or the like), deleting at least one piece of specific information of the network request with the earliest transmission time (for example, 1, 3, or 5 pieces of specific information) in the queue, and writing the latest piece of specific information of the network request, so that the latest M pieces of specific information of the network request are always stored in the target file.
Alternatively, preferably, the storage unit may be specifically configured to: if the number of the specific information of the network request stored in the target file reaches a second predetermined threshold value P (where P is greater than a positive integer of N, for example, P may be a value of 10, 20, or the like), emptying the queue, and writing the latest specific information of the network request; if the transmission 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 as to avoid storage delay.
For example, the specific information requested by the network may include, but is not limited to: sending information of the network request and returning information of the back end;
wherein the sending information of the network request comprises at least one of the following information: URL (Uniform Resource Locator) of the network request, sending time of the network request, and a page where the network request is located;
the back-end return information of the network request comprises at least one of the following information: whether the network request is successful, specific information of success of the network request, and specific information of failure of the network request.
The present application further provides an application crash information processing system, which includes the intelligent terminal 300 and the server, and therefore, the intelligent terminal 300 and the server have been described in detail in the foregoing embodiments, and are not described again here.
With regard to the apparatus and system in the above embodiments, the specific manner in which the respective units perform operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.
Fig. 4 is a schematic structural diagram of an electronic device shown in 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 (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 410 may include various types of storage units, such as system memory, Read Only Memory (ROM), and permanent storage. Wherein the ROM may store static data or instructions that are required by the processor 420 or other modules of the computer. The persistent storage device may be a read-write storage device. The persistent storage may be a non-volatile storage device that does not lose stored instructions and data even after the computer is powered off. 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 permanent storage may be a removable storage device (e.g., floppy disk, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as a dynamic random access memory. The system memory may store instructions and data that some or all of the processors require at runtime. Further, the 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 and/or optical disks, may also be employed. In some embodiments, memory 1010 may include a removable storage device that is readable and/or writable, such as a Compact Disc (CD), a read-only digital versatile disc (e.g., DVD-ROM, dual layer DVD-ROM), a read-only Blu-ray disc, an ultra-density optical disc, a flash memory card (e.g., SD card, min SD card, Micro-SD card, etc.), a magnetic floppy disc, or the like. Computer-readable storage media do not contain carrier waves or transitory electronic signals transmitted by wireless or wired means.
The memory 410 has stored thereon executable code that, when processed by the processor 420, may cause the processor 420 to perform some or all of the methods described above.
The electronic device 400 may be, for example, an intelligent terminal, or a server.
The aspects of the present application have been described in detail hereinabove with reference to the accompanying drawings. In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments. Those skilled in the art should 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 deleted according to actual needs, and the modules in the device of the embodiment of the present application may be combined, divided, and deleted 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 some 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) which, when executed by a processor of an electronic device (or electronic device, server, etc.), causes the processor to perform part or all of the various steps of the above-described method 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 applications disclosed herein may be implemented as electronic hardware, computer software, or combinations of both.
The flowchart 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.
Having described embodiments of the present application, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (12)
1. A method for processing crash information of an application program, the method comprising:
judging whether the closing of the application program is abnormal closing;
if yes, sending crash information of the application program to a server, wherein the crash information comprises a crash stack file and specific information of the stored latest N network requests; wherein N is a predetermined positive integer.
2. The method of claim 1, further comprising:
and when the application program sends a network request, storing the specific information of the network request.
3. The method of claim 2, further comprising:
when the application program is started for the first time, a target file is created locally, and the target file is used for storing specific information of a network request;
the saving of the specific information of the network request includes: and writing the specific information requested by the network into the target file.
4. The method of claim 3, further comprising:
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 queue in the target file.
5. The method of claim 4, wherein the saving the specific information of the network request comprises: and if the quantity of the specific information of the network requests stored in the target file reaches a first preset threshold value, deleting the specific information of at least one network request with the earliest sending time in the queue, and writing the latest specific information of the network request.
6. The method of claim 4, wherein the saving the specific information of the network request comprises: and if the quantity of the specific information of the network request stored in the target file reaches a second preset threshold value, emptying the queue and writing the latest specific information of the network request.
7. The method of claim 1, wherein the specific information requested by the network comprises: and sending information of the network request and back-end return information.
8. The method of claim 7, wherein the network requested transmission information comprises at least one of the following information: a Uniform Resource Locator (URL) of the network request, sending time of the network request and a page where the network request is located;
the backend return information of the network request comprises at least one of the following information: whether the network request is successful or not, specific information of success of the network request and specific information of failure of the network request.
9. The method according to any one of claims 1-8, wherein said determining whether the shutdown of the application is an abnormal shutdown comprises:
and when the application program is started, judging whether the closing of the application program is abnormal closing.
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;
a sending unit, configured to send crash information of the application program to a server when a determination result of the determining unit is yes, where the crash information includes specific information of a crash stack file and the latest N saved network requests; wherein N is a predetermined positive integer.
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 one 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 one 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 true CN113835912A (en) | 2021-12-24 |
| CN113835912B 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 (16)
| 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 |
| US20130152056A1 (en) * | 2011-12-12 | 2013-06-13 | Wayne Chang | System and method for data collection and analysis of information relating to mobile applications |
| 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 |
-
2020
- 2020-06-24 CN CN202010584333.9A patent/CN113835912B/en active Active
Patent Citations (16)
| 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 |
| US20130152056A1 (en) * | 2011-12-12 | 2013-06-13 | Wayne Chang | System and method for data collection and analysis of information relating to mobile applications |
| 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 |
| 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异常机制分析安卓应用程序崩溃", 信息技术与信息化, no. 04, pages 160 - 162 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113835912B (en) | 2024-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107391269B (en) | Method and equipment for processing message through persistent queue | |
| CN103164523A (en) | Inspection method, device and system of data consistency inspection | |
| CN110716845B (en) | Log information reading method of Android system | |
| CN108475201B (en) | Data acquisition method in virtual machine starting process and cloud computing system | |
| CN109446455B (en) | Page processing method and device | |
| KR101990329B1 (en) | Method and apparatus for improving database recovery speed using log data analysis | |
| CN110069217B (en) | Data storage method and device | |
| CN110659251B (en) | Data processing method and system and electronic equipment | |
| CN109542341B (en) | Read-write IO monitoring method, device, terminal and computer readable storage medium | |
| CN107864209B (en) | Data writing method and device and server | |
| CN116185571B (en) | Data migration method, device, storage medium and apparatus | |
| CN112416725A (en) | Pressure testing method and device | |
| CN113835912B (en) | Crash information processing method and device for application program | |
| US20200371882A1 (en) | Method, Apparatus, Device and Medium for Starting Virtual Machine | |
| CN108491160B (en) | Data writing method and device | |
| CN116594734A (en) | Container migration method and device, storage medium and electronic equipment | |
| EP3264254B1 (en) | System and method for a simulation of a block storage system on an object storage system | |
| CN108021464B (en) | Bottom-pocketing processing method and device for application response data | |
| CN111737223B (en) | File copying method, device, equipment and storage medium | |
| CN110442467B (en) | Data sharing method, terminal and computer readable storage medium | |
| US20060149732A1 (en) | Library extracting device and method for automatically extracting libraries of an embedded operating system | |
| CN106201344B (en) | Information processing method and electronic equipment | |
| CN110908821A (en) | Method, device, equipment and storage medium for task failure management | |
| CN105893394B (en) | Large file simulation method and device | |
| CN110874238A (en) | Online service updating 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 |