CN110445632B - Method and device for preventing client from crashing - Google Patents
Method and device for preventing client from crashing Download PDFInfo
- Publication number
- CN110445632B CN110445632B CN201810418618.8A CN201810418618A CN110445632B CN 110445632 B CN110445632 B CN 110445632B CN 201810418618 A CN201810418618 A CN 201810418618A CN 110445632 B CN110445632 B CN 110445632B
- Authority
- CN
- China
- Prior art keywords
- client
- data request
- information
- crash
- target parameter
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
Abstract
The invention discloses a method and a device for preventing client crash, and relates to the technical field of computers. One embodiment of the method comprises the following steps: receiving a data request of a client, and analyzing the data request to obtain target parameter information; judging whether the information responding to the data request returns to the client side to cause the client side to crash or not through a crash model according to the target parameter information; if the client crashes, the error reporting information is returned to the client. The embodiment can judge whether the client can crash or not to determine how to respond to the client, and poor experience brought to a user by direct crash is avoided.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for preventing a client from crashing.
Background
In the current mobile internet environment, 90% of the traffic comes from the mobile clients. The experience of the mobile client user is very important for the internet company, and the crash of the mobile client application software brings a very bad experience to the user. Some crashes are related to complex user environments, such as a ROM (ROM is a short for ROM image, read only memory mirror image) version of a mobile phone, a current memory of the mobile phone, a network environment, etc., and if the environments have problems, the client receives some complex messages sent by the background server again, which may cause the crashes.
In the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art:
crashes can lead to a very bad user experience and result in loss of precious user traffic. The existing communication between the client and the server is simply an interface, analysis is not performed on the complex environment of the client, and breakdown cannot be avoided.
Disclosure of Invention
In view of this, the embodiments of the present invention provide a method and apparatus for preventing a client from crashing, which can determine how to respond to a client by judging whether the client crashes, so as to avoid poor experience brought to a user by direct crashing.
To achieve the above object, according to one aspect of the embodiments of the present invention, there is provided a method for preventing a client from crashing, including receiving a data request of a client, parsing the data request to obtain target parameter information; judging whether the information responding to the data request returns to the client side to cause the client side to crash or not through a crash model according to the target parameter information; if the client crashes, the error reporting information is returned to the client.
Optionally, the method further comprises: receiving a data request of a client, and analyzing the data request to obtain target parameter information; recording the target parameter information, and issuing information responding to the data request to acquire and store the state of the client after receiving the response information; and generating a collapse model according to the target parameter information and the corresponding state thereof.
Optionally, the method further comprises: returning error reporting information to the client, wherein the client jumps to a designated address according to preset jump logic; or pop up a dialog box to prompt the user that the service is not available.
Optionally, the crash model employs a classification algorithm or a factorizer algorithm.
Optionally, the target parameter includes at least one of: platform type, system version, maximum allocated memory, current allocated total memory, remaining memory, current process CPU usage, data network, manufacturer, model, unique identification of request interface, and client application version.
In addition, according to an aspect of the embodiment of the present invention, there is provided an apparatus for preventing a client from crashing, including a receiving module, configured to receive a data request of a client, and parse the data request to obtain target parameter information; the computing module is used for judging whether the information responding to the data request is returned to the client side to cause the breakdown of the client side through a breakdown model according to the target parameter information; and the response module is used for returning error reporting information to the client if the client crashes.
Optionally, the method further comprises: the crash model generating module is used for recording the target parameter information, and issuing information responding to the data request so as to acquire and store the state of the client after receiving the response information; and generating a collapse model according to the target parameter information and the corresponding state thereof.
Optionally, the response module is further configured to: returning error reporting information to the client, wherein the client jumps to a designated address according to preset jump logic; or pop up a dialog box to prompt the user that the service is not available.
Optionally, the crash model employs a classification algorithm or a factorizer algorithm.
Optionally, the target parameter includes at least one of: platform type, system version, maximum allocated memory, current allocated total memory, remaining memory, current process CPU usage, data network, manufacturer, model, unique identification of request interface, and client application version.
According to another aspect of an embodiment of the present invention, there is also provided an electronic device including:
one or more processors;
storage means for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any of the embodiments of preventing client crashes.
According to another aspect of an embodiment of the present invention, there is also provided a computer readable medium having stored thereon a computer program, which when executed by a processor, implements the method of any of the embodiments for preventing client crashes described above.
According to still another aspect of the embodiment of the present invention, there is provided a method for preventing a client from crashing, including: transmitting a data request, wherein the target parameters in the data request include at least one of: platform type, system version, maximum allocation memory, current allocation total memory, residual memory, current process CPU utilization, data network, manufacturer, model, unique identification of request interface and client application software version; and receiving returned error reporting information.
Optionally, after receiving the returned error report information, the method further includes:
according to preset jump logic, jumping to a designated address; or pop up a dialog box to prompt the user that the service is not available.
In addition, according to another aspect of the embodiment of the present invention, there is provided an apparatus for preventing a client from crashing, including: the sending module is used for sending a data request, wherein the target parameters in the data request comprise at least one of the following: platform type, system version, maximum allocation memory, current allocation total memory, residual memory, current process CPU utilization, data network, manufacturer, model, unique identification of request interface and client application software version; and the receiving module is used for receiving the returned error reporting information.
Optionally, after the receiving module receives the returned error report information, the receiving module is further configured to:
according to preset jump logic, jumping to a designated address; or pop up a dialog box to prompt the user that the service is not available.
According to another aspect of an embodiment of the present invention, there is also provided an electronic device including:
one or more processors;
storage means for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any of the embodiments of preventing client crashes.
According to another aspect of an embodiment of the present invention, there is also provided a computer readable medium having stored thereon a computer program, which when executed by a processor, implements the method of any of the embodiments for preventing client crashes described above.
One embodiment of the above invention has the following advantages or benefits: when a client requests data from a server, the server judges whether a message responding to the request is too complex for the client or may cause breakdown according to target parameter information contained in the request of the client. If the judgment is that the crash is caused, the control is issued to avoid the crash caused by the client receiving the response message.
Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main flow of a method for preventing client crashes according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of the main flow of a method for preventing client crashes according to a referenceable embodiment of the invention;
FIG. 3 is a schematic diagram of the main modules of an apparatus for preventing client crashes according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of the main modules of an apparatus for preventing client crashes according to a referenceable embodiment of the invention;
FIG. 5 is a schematic diagram of the main flow of a method for preventing client crashes applied to a client according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of the main modules of an apparatus for preventing client crashes applied to a client according to an embodiment of the present invention;
FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;
fig. 8 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a method for preventing a client crash according to an embodiment of the present invention, as shown in fig. 1, the method for preventing a client crash includes:
step S101, receiving a data request of a client, and analyzing the data request to obtain target parameter information.
In an embodiment, the target parameter may include at least one of: platform type (platform), system version (OSversion), maximum allocation memory (MemMax), current allocation total memory (MemTotal), remaining memory (MemFree), current process CPU utilization (CPU utilization), data network (communication mode), manufacturer (manufacturer), model (model), unique identification of request interface (function id), and client application version (appVersion). Wherein the platform type is android or ios, the system version is android8.0 or ios11.1, and the manufacturer is Hua Cheng, setaria, apple, etc.
Step S102, judging whether the information responding to the data request is returned to the client side to cause the client side to crash or not through a crash model according to the target parameter information.
In an embodiment, the target parameter information is substituted into the crash model, and the obtained calculation result indicates normal (not causing the client to crash) if 0, and indicates crash (causing the client to crash) if 1.
The crash model may be a predicted result of whether the call crashes or not by inputting a target parameter. Preferably, the crash model may employ classification algorithms, factorers FM, and the like.
Step S103, if the client crashes, the error reporting information is returned to the client.
Preferably, if the calculation result obtained in step S102 is 0, that is, normal, response information is obtained according to the data request, and then the response information is returned to the client. And if the calculation result obtained in the step S102 is 1, namely, a crash is performed, returning to the client according to error information (error) in a preset format.
Preferably, after the error reporting information in the predetermined format is returned to the client, the user can be prompted to crash the client if normal response information is received. Further, a dialog box may be popped up to prompt the user that the service is not available, or to present a default text, picture.
In addition, the flow can be distributed elsewhere, and the specific implementation process is as follows: the jump logic may be preset at the client, and after receiving the error message in the predetermined format, jump to the designated address, such as a similar commodity.
It can be seen that according to the method for preventing client crash described above, it can be determined whether the message responding to the request is too complex for the client or may cause a crash according to the received client data request. If the judgment is that the crash is caused, the control is issued to avoid the crash caused by the client receiving the response message. The invention can avoid the problem of the user environment, such as the ROM version of the mobile phone, the current memory of the mobile phone, the network environment, and the like, which causes the client to receive the complex message sent by the background server to cause breakdown.
In addition, in the method for preventing client crash, the crash can be the flashing back of the application program.
As a reference embodiment of the present invention, as shown in fig. 2, the crash model may be obtained by:
step S201: and receiving a data request of the client, and analyzing the data request to obtain target parameter information.
Step S202: and recording the target parameter information and issuing information responding to the data request.
Step S203: and acquiring and storing the state of the client after receiving the response information.
The obtained state of the client after receiving the response information includes normal and crash, preferably, the state is set to 0 normally, the crash is set to 1, that is, the state is marked as 0 if the state is normal, and the state is marked as 1 if the state is crash. As an embodiment, both the target parameter information and the corresponding state may be recorded in a preset table to be saved.
Step S204: whether the predetermined number of target parameter information and the corresponding states thereof are obtained is determined, if yes, step S205 is performed, otherwise step S201 is returned.
Wherein the predetermined number of target parameter information and the corresponding states thereof constitute history data. Preferably, the historical data is used for model training, and the number of positive and negative samples is as large as possible.
Step S205: a crash model is generated.
The crash model may be a predicted result of whether the call crashes or not by inputting a target parameter.
Preferably, the crash model may employ classification algorithms, factorers FM, and the like.
It should be noted that, since the factoring machine FM considers the relationships between the weights in the model, and the relationships between the features, the following factoring machine FM (Factorization Machine) may be preferably used as the crash model.
Where v ε Rn, k, < vi, vj > represents the dot product between two vectors of size k, k being the dimension of the hidden vector:
x is the number i x j These represent values of target parameters platform, OSversion, memMax, memTotal, memFree, cpuUsed, communicationMode, manufactor, model, functionId and appVersion.
w i Representative is x i Is the optimal parameter inside the collapse model calculated by the residual function gradient descent method. The matrix decomposition of the FM factorizer is based on an assumption that the values in the matrix are equal to the product of the two learned hidden vectors, i.e., w ij ＝v i v j Two of the features v i 、v j Is a parameter w for the interrelationship of (a) ij And (3) representing.
In an embodiment, whether the data request of the normally responding client will cause the crash can be predicted according to the target parameter information of the client through the generated crash model. When the data request of the response client side causes the breakdown, the error reporting information can be returned so as to avoid the breakdown of the client side. The Crash may refer to the flashing back of the application APP, i.e. Crash.
Fig. 3 is an apparatus for preventing a client crash according to an embodiment of the present invention, and as shown in fig. 3, the apparatus 300 for preventing a client crash includes a receiving module 301, a calculating module 302, and a responding module 303. The receiving module 301 receives a data request of a client, and parses the data request to obtain target parameter information. The calculation module 302 then determines, based on the target parameter information, whether the client has crashed if information to respond to the data request is returned to it via a crash model. If the client crashes, the response module 303 returns the error report to the client.
It should be noted that the target parameters may include at least one of the following: platform type (platform), system version (OSversion), maximum allocation memory (MemMax), current allocation total memory (MemTotal), remaining memory (MemFree), current process CPU utilization (CPU utilization), data network (communication mode), manufacturer (manufacturer), model (model), unique identification of request interface (function id), and client application version (appVersion).
In a preferred embodiment, the device for preventing client crash further includes a crash model generating module 304 (as shown in fig. 4), and the crash model generating module 304 records the target parameter information, and issues information responding to the data request, so as to obtain and save the state of the client after receiving the response information. Then, according to the target parameter information and the corresponding state, a breakdown model is generated.
Further, the crash model may be a predicted result of whether the call crashes or not by inputting the target parameter. Still further, the crash model may employ classification algorithms, factorers FM, and the like.
As an embodiment, the response module 303 may return the error report to the client, where the client jumps to the specified address according to the preset jump logic. Or a dialog box may be popped up to prompt the user that the service is not available.
It should be noted that, in the embodiment of the device for preventing client crash of the present invention, the method for preventing client crash has been described in detail, so that the description is not repeated here.
Fig. 5 is a method for preventing a client from crashing, as shown in fig. 5, applied to a client, according to an embodiment of the present invention, the method for preventing a client from crashing includes:
step S501, a data request is sent, where a target parameter in the data request includes at least one of the following: platform type, system version, maximum allocated memory, current allocated total memory, remaining memory, current process CPU usage, data network, manufacturer, model, unique identification of request interface, and client application version.
Step S502, receiving returned error reporting information.
Preferably, after receiving the error report information returned by the server, the user can jump to the designated address according to the preset jump logic. Or a dialog box may be popped up to prompt the user that the service is not available.
It can be seen that, after the data request is sent, if the server predicts that the client will crash after receiving the data of the normal response, the client will receive the error report information returned by the server.
Fig. 6 is an apparatus for preventing a client crash according to an embodiment of the present invention, and as shown in fig. 6, the apparatus 600 for preventing a client crash includes a transmitting module 601 and a receiving module 602. Wherein the sending module 601 may send a data request, wherein the target parameter in the data request includes at least one of: platform type, system version, maximum allocated memory, current allocated total memory, remaining memory, current process CPU usage, data network, manufacturer, model, unique identification of request interface, and client application version. The receiving module 602 may receive the returned error report.
Preferably, after receiving the returned error message, the receiving module 602 may jump to the designated address according to a preset jump logic. Or a dialog box may be popped up to prompt the user that the service is not available.
FIG. 7 illustrates an exemplary system architecture 700 of a method of preventing client crashes or an apparatus of preventing client crashes that may be applied to a server to which embodiments of the present invention may be applied. Or FIG. 7 illustrates an exemplary system architecture 700 of a method of preventing client crashes or an apparatus of preventing client crashes that may be applied to clients with embodiments of the present invention.
As shown in fig. 7, a system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 is the medium used to provide communication links between the terminal devices 701, 702, 703 and the server 705. The network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 705 via the network 704 using the terminal devices 701, 702, 703 to receive or send messages or the like. Various communication client applications such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 701, 702, 703.
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 705 may be a server providing various services, such as a background management server (by way of example only) providing support for shopping-type websites browsed by users using the terminal devices 701, 702, 703. The background management server may analyze and process the received data such as the product information query request, and feedback the processing result (e.g., the target push information, the product information—only an example) to the terminal device.
It should be noted that, the method for preventing client crash provided in the embodiment of the present invention is generally executed by the server 705, and accordingly, the device for preventing client crash is generally disposed in the server 705.
It should be understood that the number of terminal devices, networks and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 8, there is illustrated a schematic diagram of a computer system 800 suitable for use in implementing an embodiment of the present invention. The terminal device shown in fig. 8 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU) 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM803, various programs and data required for the operation of the system 800 are also stored. The CPU801, ROM 802, and RAM803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to the bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 801.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. 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 or flowchart illustration, and combinations of blocks in the block diagrams 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 modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor includes a receiving module, a computing module, and a responding module. The names of these modules do not constitute a limitation on the module itself in some cases.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include: receiving a data request of a client, and analyzing the data request to obtain target parameter information; judging whether the information responding to the data request returns to the client side to cause the client side to crash or not through a crash model according to the target parameter information; if the client crashes, the error reporting information is returned to the client.
According to the technical scheme provided by the embodiment of the invention, whether the client can be crashed or not can be judged to determine how to respond to the client, and poor experience brought to a user by direct crashing is avoided.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (18)
1. A method for preventing client crashes, comprising:
receiving a data request of a client, and analyzing the data request to obtain target parameter information;
judging whether the information responding to the data request returns to the client side to cause the client side to crash or not through a crash model according to the target parameter information;
if the client crashes, the error reporting information is returned to the client.
2. The method as recited in claim 1, further comprising:
receiving a data request of a client, and analyzing the data request to obtain target parameter information;
recording the target parameter information, and issuing information responding to the data request to acquire and store the state of the client after receiving the response information;
and generating a collapse model according to the target parameter information and the corresponding state thereof.
3. The method as recited in claim 1, further comprising:
returning error reporting information to the client, wherein the client jumps to a designated address according to preset jump logic; or pop up a dialog box to prompt the user that service is not available.
4. The method of claim 1, wherein the crash model employs a classification algorithm or a factorizer algorithm.
5. The method of any one of claims 1-4, wherein the target parameter comprises at least one of: platform type, system version, maximum allocated memory, current allocated total memory, remaining memory, current process CPU usage, data network, manufacturer, model, unique identification of request interface, and client application version.
6. An apparatus for preventing client crashes, comprising:
the receiving module is used for receiving the data request of the client and analyzing the data request to obtain target parameter information;
the computing module is used for judging whether the information responding to the data request is returned to the client side to cause the breakdown of the client side through a breakdown model according to the target parameter information;
and the response module is used for returning error reporting information to the client if the client crashes.
7. The apparatus as recited in claim 6, further comprising:
the crash model generating module is used for recording the target parameter information, and issuing information responding to the data request so as to acquire and store the state of the client after receiving the response information; and generating a collapse model according to the target parameter information and the corresponding state thereof.
8. The apparatus of claim 6, wherein the response module is further configured to:
returning error reporting information to the client, wherein the client jumps to a designated address according to preset jump logic; or pop up a dialog box to prompt the user that service is not available.
9. The apparatus of claim 6, wherein the crash model employs a classification algorithm or a factorizer algorithm.
10. The apparatus of any of claims 6-9, wherein the target parameter comprises at least one of: platform type, system version, maximum allocated memory, current allocated total memory, remaining memory, current process CPU usage, data network, manufacturer, model, unique identification of request interface, and client application version.
11. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-5.
12. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-5.
13. A method for preventing client crashes, comprising:
transmitting a data request, wherein the target parameters in the data request include at least one of: platform type, system version, maximum allocation memory, current allocation total memory, residual memory, current process CPU utilization, data network, manufacturer, model, unique identification of request interface and client application software version;
receiving error reporting information returned by the method of claim 1.
14. The method of claim 13, further comprising, after receiving the returned error message:
according to preset jump logic, jumping to a designated address; or pop up a dialog box to prompt the user that service is not available.
15. An apparatus for preventing client crashes, comprising:
the sending module is used for sending a data request, wherein the target parameters in the data request comprise at least one of the following: platform type, system version, maximum allocation memory, current allocation total memory, residual memory, current process CPU utilization, data network, manufacturer, model, unique identification of request interface and client application software version;
and the receiving module is used for receiving the error reporting information returned by the method as claimed in claim 1.
16. The apparatus of claim 15, wherein after the receiving module receives the returned error message, the receiving module is further configured to:
according to preset jump logic, jumping to a designated address; or pop up a dialog box to prompt the user that service is not available.
17. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 13 or 14.
18. A computer readable medium on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 13 or 14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810418618.8A CN110445632B (en) | 2018-05-04 | 2018-05-04 | Method and device for preventing client from crashing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810418618.8A CN110445632B (en) | 2018-05-04 | 2018-05-04 | Method and device for preventing client from crashing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110445632A CN110445632A (en) | 2019-11-12 |
| CN110445632B true CN110445632B (en) | 2023-09-01 |
Family
ID=68427526
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810418618.8A Active CN110445632B (en) | 2018-05-04 | 2018-05-04 | Method and device for preventing client from crashing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110445632B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111416857A (en) * | 2020-03-16 | 2020-07-14 | 广州市百果园信息技术有限公司 | Client crash processing method, device, system, equipment and storage medium |
| CN111709778B (en) * | 2020-05-29 | 2023-04-07 | 北京百度网讯科技有限公司 | Travel flow prediction method and device, electronic equipment and storage medium |
| CN113742377A (en) * | 2020-11-04 | 2021-12-03 | 北京沃东天骏信息技术有限公司 | Method and device for processing data |
| CN117278524A (en) * | 2023-09-26 | 2023-12-22 | 北京网藤科技有限公司 | Method and system for solving problem of displaying warning prompt when browser opens local server |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102393842A (en) * | 2011-06-28 | 2012-03-28 | 用友软件股份有限公司 | Command processing device and command processing method |
| CN103019879A (en) * | 2013-01-07 | 2013-04-03 | 北京奇虎科技有限公司 | Method and system for processing crash information of browser |
| CN103077108A (en) * | 2013-01-07 | 2013-05-01 | 北京奇虎科技有限公司 | Method and system for warning browser crash |
| CN103226486A (en) * | 2013-04-23 | 2013-07-31 | 北京奇虎科技有限公司 | Optimization method and device for browser operation |
| US8707433B1 (en) * | 2011-05-03 | 2014-04-22 | Symantec Corporation | Fake exception handler detection |
| CN104506658A (en) * | 2015-01-13 | 2015-04-08 | 厦门美图之家科技有限公司 | Early-warning method and system for collapse of application program |
| CN104572327A (en) * | 2014-12-24 | 2015-04-29 | 北京奇虎科技有限公司 | Method, device and system for processing browser crash |
| CN106156064A (en) * | 2015-03-30 | 2016-11-23 | 阿里巴巴集团控股有限公司 | Data base is carried out the method and device of flow-control |
| CN106201442A (en) * | 2016-07-15 | 2016-12-07 | 广东欧珀移动通信有限公司 | The execution method and device of application program |
| WO2017000480A1 (en) * | 2015-07-01 | 2017-01-05 | 中兴通讯股份有限公司 | Time synchronization method, server and system, and storage medium |
| WO2017107438A1 (en) * | 2015-12-25 | 2017-06-29 | 乐视控股（北京）有限公司 | Method for controlling reporting of crash data, server and client |
| CN107102928A (en) * | 2017-04-18 | 2017-08-29 | 广州视源电子科技股份有限公司 | A kind of application crash information uploading method and device |
| CN107172122A (en) * | 2017-03-31 | 2017-09-15 | 北京奇艺世纪科技有限公司 | A kind of abnormality eliminating method and device |
| CN107506256A (en) * | 2017-09-07 | 2017-12-22 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of crash data monitoring |
| CN107729931A (en) * | 2017-10-09 | 2018-02-23 | 北京京东尚科信息技术有限公司 | Picture methods of marking and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7380171B2 (en) * | 2004-12-06 | 2008-05-27 | Microsoft Corporation | Controlling software failure data reporting and responses |
| US9268547B2 (en) * | 2010-01-11 | 2016-02-23 | Ensighten, Inc. | Conditional logic for delivering computer-executable program instructions and content |
| CA2762696C (en) * | 2011-12-20 | 2018-11-20 | Ibm Canada Limited - Ibm Canada Limitee | Client selectable server-side error resolution |
| RU2016130451A (en) * | 2013-12-30 | 2018-02-07 | Общество с ограниченной ответственностью "Мэйл.Ру" | METHOD AND SYSTEM OF ASSISTANCE TO THE USER IN EMERGENCY COMPLETIONS OF THE SOFTWARE APPLICATION |
| AU2015235840A1 (en) * | 2014-03-27 | 2016-08-18 | Alert Logic, Inc. | Malicious software identification integrating behavioral analytics and hardware events |
-
2018
- 2018-05-04 CN CN201810418618.8A patent/CN110445632B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8707433B1 (en) * | 2011-05-03 | 2014-04-22 | Symantec Corporation | Fake exception handler detection |
| CN102393842A (en) * | 2011-06-28 | 2012-03-28 | 用友软件股份有限公司 | Command processing device and command processing method |
| CN103019879A (en) * | 2013-01-07 | 2013-04-03 | 北京奇虎科技有限公司 | Method and system for processing crash information of browser |
| CN103077108A (en) * | 2013-01-07 | 2013-05-01 | 北京奇虎科技有限公司 | Method and system for warning browser crash |
| CN103226486A (en) * | 2013-04-23 | 2013-07-31 | 北京奇虎科技有限公司 | Optimization method and device for browser operation |
| CN104572327A (en) * | 2014-12-24 | 2015-04-29 | 北京奇虎科技有限公司 | Method, device and system for processing browser crash |
| CN104506658A (en) * | 2015-01-13 | 2015-04-08 | 厦门美图之家科技有限公司 | Early-warning method and system for collapse of application program |
| CN106156064A (en) * | 2015-03-30 | 2016-11-23 | 阿里巴巴集团控股有限公司 | Data base is carried out the method and device of flow-control |
| WO2017000480A1 (en) * | 2015-07-01 | 2017-01-05 | 中兴通讯股份有限公司 | Time synchronization method, server and system, and storage medium |
| WO2017107438A1 (en) * | 2015-12-25 | 2017-06-29 | 乐视控股（北京）有限公司 | Method for controlling reporting of crash data, server and client |
| CN106201442A (en) * | 2016-07-15 | 2016-12-07 | 广东欧珀移动通信有限公司 | The execution method and device of application program |
| CN107172122A (en) * | 2017-03-31 | 2017-09-15 | 北京奇艺世纪科技有限公司 | A kind of abnormality eliminating method and device |
| CN107102928A (en) * | 2017-04-18 | 2017-08-29 | 广州视源电子科技股份有限公司 | A kind of application crash information uploading method and device |
| CN107506256A (en) * | 2017-09-07 | 2017-12-22 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of crash data monitoring |
| CN107729931A (en) * | 2017-10-09 | 2018-02-23 | 北京京东尚科信息技术有限公司 | Picture methods of marking and device |
Non-Patent Citations (1)
| Title |
|---|
| 网络高负载下的崩溃估计模型仿真;张杰;景雯;张景安;;计算机仿真(第09期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110445632A (en) | 2019-11-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110445632B (en) | Method and device for preventing client from crashing | |
| US20180183651A1 (en) | Content push method and server, and terminal | |
| CN111818136A (en) | Data processing method and device, electronic equipment and computer readable medium | |
| US20200327001A1 (en) | Message processing method and system, storage medium and electronic device | |
| CN113076153B (en) | Interface calling method and device | |
| CN112379982B (en) | Task processing method, device, electronic equipment and computer readable storage medium | |
| CN110650209A (en) | Method and device for realizing load balance | |
| WO2022257604A1 (en) | Method and apparatus for determining user tag | |
| CN112650804B (en) | Big data access method, device, system and storage medium | |
| CN113761565B (en) | Data desensitization method and device | |
| CN109949806B (en) | Information interaction method and device | |
| CN111831503B (en) | Monitoring method based on monitoring agent and monitoring agent device | |
| EP3723343B1 (en) | Resource processing method and system, storage medium and electronic device | |
| CN108011964B (en) | Picture uploading method and device, electronic terminal and readable storage medium | |
| CN111385150A (en) | Method and device for acquiring information | |
| CN108400929B (en) | Data processing method, device, computing equipment and medium | |
| CN113282489B (en) | Interface testing method and device | |
| CN115470432A (en) | Page rendering method and device, electronic equipment and computer readable medium | |
| CN114924937A (en) | Batch task processing method and device, electronic equipment and computer readable medium | |
| CN111580882B (en) | Application program starting method, device, computer system and medium | |
| CN114356713A (en) | Thread pool monitoring method and device, electronic equipment and storage medium | |
| CN113660699A (en) | Intelligent cluster networking method and device and electronic equipment | |
| CN113743425A (en) | Method and device for generating classification model | |
| CN113282455A (en) | Monitoring processing method and device | |
| CN109840073B (en) | Method and device for realizing business process |
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 |