CN102681874B - A kind ofly guarantee the method that software normally runs and device - Google Patents
A kind ofly guarantee the method that software normally runs and device Download PDFInfo
- Publication number
- CN102681874B CN102681874B CN201210148916.2A CN201210148916A CN102681874B CN 102681874 B CN102681874 B CN 102681874B CN 201210148916 A CN201210148916 A CN 201210148916A CN 102681874 B CN102681874 B CN 102681874B
- Authority
- CN
- China
- Prior art keywords
- client software
- flash
- software
- state information
- flash back
- 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
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000008439 repair process Effects 0.000 claims abstract description 18
- 206010016754 Flashback Diseases 0.000 claims description 174
- 230000002159 abnormal effect Effects 0.000 claims description 28
- 238000012544 monitoring process Methods 0.000 claims description 17
- 238000009434 installation Methods 0.000 claims description 5
- 210000003205 muscle Anatomy 0.000 abstract 5
- 238000005457 optimization Methods 0.000 abstract 1
- 230000008569 process Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Landscapes
- Computer And Data Communications (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses and a kind ofly guarantee the method that software normally runs and device, belong to field of computer technology.Described method comprises: when needs startup optimization client software, move back status information judge the sudden strain of a muscle of described client software; If it is that state is moved back in sudden strain of a muscle that status information is moved back in described sudden strain of a muscle, then number of times is moved back in the sudden strain of a muscle increasing described client software, moves back number of times determine whether described client software can be used according to described sudden strain of a muscle; If unavailable, then repair described client software and start described client software after repair.Described device comprises: judge module, determination module and reparation module.The present invention can guarantee that software normally runs.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for ensuring normal operation of software.
Background
With the development of computer technology, a variety of client software capable of implementing various functions, such as chat client software capable of chatting, are developed. In the running process of the client software, the client software has a flash back (blast) problem for various reasons.
The client software is started by a user, wherein the problem of flash back is inevitable in client software, many client software have the problem of flash back, and the user can restart the client software after the problem of flash back occurs; sometimes, a serious problem occurs in the client software, for example, the user data of the client software is damaged, which may cause a problem of flash back of the client software every time the user starts to run the client software, so that the client software cannot run normally.
Disclosure of Invention
In order to ensure the normal operation of client software, the invention provides a method and a device for ensuring the normal operation of software. The technical scheme is as follows:
a method of ensuring proper functioning of software, the method comprising:
when the client software needs to be started and operated, judging the flash back state information of the client software, wherein the flash back state information is used for recording whether the client software has a flash back problem or not when the client software is started and operated last time;
if the information of the flash quit state is the flash quit state, increasing the flash quit times of the client software, and determining whether the client software is available according to the flash quit times;
if not, the client software is repaired and started after repair.
The determining whether the client software is available according to the number of flash backs includes:
and judging the flash back frequency, if the flash back frequency does not exceed the preset frequency, determining that the client software is available, and if the flash back frequency exceeds the preset frequency, determining that the client software is unavailable.
The repairing the client software and starting the client software after the repairing includes:
downloading the client software of the latest version, installing the client software of the latest version to realize the restoration of the client software, and starting the client software of the latest version after installation; or,
the method comprises the steps of obtaining a data directory corresponding to the client software, deleting the data directory, starting the client software, creating the data directory after the client software is started, and obtaining and loading user data into the created data directory by the client software so as to repair the user data corresponding to the client software.
If the flash back state information is a non-flash back state or the client software is available, the method further comprises:
and setting the flash quit state information of the client software to be a flash quit state, starting the client software and monitoring the client software.
The method further comprises the following steps:
and if the client software does not have the flash back problem before the client software finishes loading the main interface of the client software, starting timing when the client software finishes loading the main interface of the client software.
The method further comprises the following steps:
and if the client software has no flash quit problem before the timed time reaches the preset time, setting the flash quit state information of the client software to be in a non-flash quit state when the timed time reaches the preset time.
After the monitoring of the client software, the method further comprises:
if the client software is monitored to operate, the operating state information of the operation is set to be in an abnormal state, and if the client software does not have the problem of flash back before the client software finishes loading the main interface of the client software, the operating state information of the operation is set to be in a normal state when the client software finishes loading the main interface of the client software.
The method further comprises the following steps:
and when the client software is monitored to finish loading the main interface of the client software, setting the running state information of the client software to be in an abnormal state, and if the client software does not have the problem of flash back before the timed time reaches the preset time, setting the running state information of the client carbonyl software to be in a normal state when the timed time reaches the preset time.
If the flash quit state information is a non-flash quit state, before the flash quit state information of the client software is set to be the flash quit state, the method further comprises the following steps:
and clearing the flash back times of the client software.
An apparatus for ensuring proper operation of software, the apparatus comprising:
the judging module is used for judging the flash back state information of the client software when the client software needs to be started and operated, wherein the flash back state information is used for recording whether the client software has a flash back problem when the client software is started and operated last time;
the determining module is used for increasing the flash back times of the client software if the flash back state information is in a flash back state, and determining whether the client software is available according to the flash back times;
and the repairing module is used for repairing the client software and starting the client software after repairing if the determining module determines that the client software is unavailable.
The determining module is specifically configured to determine the number of times of flash back, determine that the client software is available if the number of times of flash back does not exceed a preset number of times, and determine that the client software is unavailable if the number of times of flash back exceeds the preset number of times.
The repair module includes:
the downloading unit is used for downloading the client software of the latest version, installing the client software of the latest version to realize the restoration of the client software and starting the client software of the latest version after installation; or,
and the deleting unit is used for acquiring a data directory corresponding to the client software, deleting the data directory, starting the client software, creating the data directory after the client software is started, and acquiring and loading user data into the created data directory by the client software so as to repair the user data corresponding to the client software.
If the information of the flash back state is a non-flash back state or the client software is available, the device further comprises:
and the first setting module is used for setting the flash quit state information of the client software to be a flash quit state, starting the client software and monitoring the client software.
The device further comprises:
and the timing module is used for starting timing when the client software is monitored to finish loading the main interface of the client software if the client software does not have the flash back problem before finishing loading the main interface of the client software.
The device further comprises:
and the second setting module is used for setting the flash quit state information of the client software into a non-flash quit state when the timed time reaches the preset time if the client software does not have the flash quit problem before the timed time reaches the preset time.
The device further comprises:
and the third setting module is used for setting the operating state information of the operation to be in an abnormal state if the client software is monitored to operate, and setting the operating state information of the operation to be in a normal state if the client software does not have a flash back problem before the client software finishes loading the main interface of the client software.
The device further comprises:
and the third setting module is used for setting the running state information of the client software to be in an abnormal state when the client software is monitored to finish loading the main interface of the client software, and if the client software does not have the problem of flash back before the timed time reaches the preset time, setting the running state information of the client carbonyl software to be in a normal state when the timed time reaches the preset time.
If the flash back state information is a non-flash back state, the apparatus further comprises:
and the zero clearing module is used for clearing the flash back times of the client software.
In the embodiment of the invention, when the client software needs to be started and operated, the flash back state information of the client software is judged, if the flash back state information is in a flash back state, the flash back times of the client software are increased, whether the client software is available or not is determined according to the flash back times, if the client software is not available, the client software is repaired, and the client software is started after the client software is repaired. Therefore, whether the client software is available or not can be determined, and when the client software is determined to be unavailable, the client software is repaired to ensure that the client software operates normally.
Drawings
Fig. 1 is a flowchart of a method for ensuring normal operation of software according to embodiment 1 of the present invention;
fig. 2 is a flowchart of a method for ensuring normal operation of software according to embodiment 2 of the present invention;
fig. 3 is a schematic structural diagram of an apparatus for ensuring normal operation of software according to embodiment 3 of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
Example 1
As shown in fig. 1, an embodiment of the present invention provides a method for ensuring normal operation of software, including:
step 101: when the client software needs to be started and operated, judging the flash back state information of the client software;
step 102: if the information of the flash quit state is the flash quit state, increasing the flash quit times of the client software, and determining whether the client software is available according to the flash quit times;
step 103: if not, the client software is repaired and started after the repair.
In the embodiment of the invention, when the client software needs to be started and operated, the flash back state information of the client software is judged, if the flash back state information is in a flash back state, the flash back times of the client software are increased, whether the client software is available or not is determined according to the flash back times, if the client software is not available, the client software is repaired, and the client software is started after the client software is repaired. Therefore, whether the client software is available or not can be determined, and when the client software is determined to be unavailable, the client software is repaired to ensure that the client software operates normally.
Example 2
As shown in fig. 2, an embodiment of the present invention provides a method for ensuring normal operation of software, including:
step 201: when the client software needs to be started and operated, judging the flash back state information of the client software, if the flash back state information is in a non-flash back state, executing step 202, and if the flash back state is in a flash back state, executing step 203;
the client software is used for recording whether the client software has the problem of flash back when the client software is started and operated last time, if the client software has the problem of flash back when the client software is started and operated last time, the flash back state information of the client software is in a flash back state, and if the client software has no problem of flash back when the client software is started and operated last time, the flash back state information of the client software is in a non-flash back state.
Among them, the flash back problem is an unavoidable problem of many client software, and the client software often has the flash back problem in the following first stage, second stage or third stage: the first stage is a time period from the time when the client software is started to the time before a main interface of the client software is loaded, and the operation performed by the client software in the first stage is software initialization operation; the second stage is a process that the client software loads a main interface of the client software, and the client software performs an account initialization operation within the time of the second stage; and the third stage is that the client software starts to run after loading the main interface within the preset time after the client software loads the main interface.
Step 202: clearing the flash back times corresponding to the client software, and then executing step 204;
the flash back times corresponding to the client software are used for recording the times of flash back problems when the client software is continuously started and operated.
Step 203: increasing the flash back times of the client software, determining whether the client software is available according to the increased flash back times, if so, executing step 204, and if not, executing step 207;
specifically, the number of times of flash back of the client software is increased, the size of the increased number of times of flash back is judged, if the increased number of times of flash back does not exceed the preset number of times, the client software is determined to be usable, and if the increased number of times of flash back exceeds the preset number of times, the client software is determined to be unusable.
Step 204: setting the flash quit state information of the client software into a flash quit state, starting the client software and monitoring the client software;
the client software often issues a flash back problem in the first stage, the second stage, or the third stage, so each operation performed by the client software is monitored in the first stage, the second stage, and the third stage.
Wherein, the client software performs software initialization operation in the first stage; further, in the first stage, when the client software is monitored to perform software initialization operation, the operating state information of the software initialization operation performed by the client software is set to be in an abnormal state, and if the client software does not have a flash back problem before the client software completes the software initialization operation, the operating state information of the software initialization operation is set to be in a normal state after the client software is monitored to complete the software initialization operation.
If the client software has the flash back problem before the client software completes the software initialization operation, all operations are finished, and accordingly, the flash back state information of the client software is in a flash back state, that is, the flash back problem of the client software during the current startup operation is recorded, and the operation state information of the software initialization operation is in an abnormal state, so that a technician can determine that the flash back problem of the client software during the software initialization operation is caused.
The software initialization operation of the client software generally comprises a storage initialization operation and a registration operation, or comprises a storage initialization operation and a login operation; further, when the monitoring client software starts to perform the storage initialization operation, the operation state information of the storage initialization operation performed by the client software is set to be in an abnormal state, and if the client software does not have a flash back problem before the client software performs the storage initialization operation, the operation state information of the storage initialization operation is set to be in a normal state after the monitoring client software performs the storage initialization operation.
If the client software is subjected to the flash quitting before the storage initialization operation of the client software is finished, all operations are finished, correspondingly, the flash quitting state information of the client software is in a flash quitting state, namely, the problem that the client software is subjected to the flash quitting when the client software is started and operated at this time is recorded, and the operation state information of the storage initialization operation is in an abnormal state, so that a technician can determine that the problem that the client software is subjected to the flash quitting when the storage initialization operation is carried out.
After the storage initialization operation is performed by the client software, the client software performs a registration operation or a login operation.
Further, if the registration operation is started after the storage initialization operation of the monitored client software is completed, the operation state information of the registration operation is set to be in an abnormal state, and if the client software does not have the problem of flash back before the registration operation of the monitored client software is completed, the operation state information of the registration operation is set to be in a normal state after the registration operation of the monitored client software is completed.
If the client software has the problem of flash quit before the client software finishes the registration operation, all the operations are finished, correspondingly, the flash quit state information of the client software is in a flash quit state, namely the flash quit problem of the client software during the current starting operation is recorded, and the operation state information of the registration operation is in an abnormal state, so that a technician can determine that the flash quit problem of the client software during the registration operation is caused.
Further, if the login operation is started after the storage initialization operation of the monitored client software is completed, the operating state information of the login operation is set to be in an abnormal state, and if the problem of flash back of the client software does not occur before the login operation of the client software is completed, the operating state information of the login operation is set to be in a normal state after the login operation of the monitored client software is completed.
If the client software has the problem of flash back before the client software finishes the login operation, all operations are finished, correspondingly, the flash back state information of the client software is in a flash back state, namely the flash back problem of the client software during the current starting operation is recorded, and the operation state information of the stored login operation is in an abnormal state, so that a technician can determine that the flash back problem of the client software during the login operation is caused.
After the software initialization operation is executed by the client software, entering the second stage, and performing account initialization operation on the client software in the second stage; further, when the monitoring client software starts to perform account initialization operation, the operation state information of the account initialization operation performed by the client software is set to be in an abnormal state, and if the client software does not have a problem of flash back before the client software finishes account initialization operation, the operation state information of the account initialization operation is set to be in a normal state after the monitoring client software finishes account initialization operation.
If the client software has the problem of flash back before the client software finishes account initialization operation, all operations are finished, correspondingly, the flash back state information of the client software is in a flash back state, namely the flash back problem of the client software during the current starting operation is recorded, and the operation state information of the account initialization operation is in an abnormal state, so that technicians can determine that the flash back problem occurs when the client software performs the account initialization operation.
Wherein, the account initialization operation of the client software generally comprises a message list loading operation and a contact list loading operation.
Further, when the monitoring client software starts to perform the message list loading operation, the operating state information of the message list loading operation performed by the client software is set to be in an abnormal state, and if the client software does not have a flash back problem before the client software finishes the message list loading operation, the operating state information of the message list loading operation is set to be in a normal state after the monitoring client software finishes the message list loading operation.
If the client software has a flash back problem before the client software finishes the operation of loading the message list, all the operations are finished, correspondingly, the flash back state information of the client software is in a flash back state, namely the flash back problem of the client software during the current starting operation is recorded, and the operation state information of the operation of loading the message list is in an abnormal state, so that a technician can determine that the flash back problem occurs when the client software performs the operation of loading the message list.
Further, when the client software starts to load the contact list, the operating state information of the contact list loading operation performed by the client software is set to be in an abnormal state, and if the client software does not have a flash back problem before the client software finishes the contact list loading operation, the operating state information of the contact list loading operation is set to be in a normal state after the client software finishes the contact list loading operation.
If the client software has a flash back problem before the client software finishes the operation of loading the contact list, all the operations are finished, correspondingly, the flash back state information of the client software is in a flash back state, namely the flash back problem of the client software during the current starting operation is recorded, and the operation state information of the operation of loading the contact list is in an abnormal state, so that a technician can determine that the flash back problem occurs when the client software loads the contact list according to the operation state information.
The client software finishes the account initialization operation to realize the loading of the main interface, so that the client software finishes the account initialization operation to finish the loading of the main interface.
Step 205: if the client software does not have the problem of flash back before the client software finishes loading the own main interface, timing is started when the client software finishes monitoring the main interface loading;
the client software finishes loading the main interface of the client software, namely the client software finishes the first stage and the second stage, and enters a third stage after finishing loading the main interface of the client software, and the client software starts to run in the third stage.
Further, when the client software is monitored to finish loading the main interface of the client software, the running state information of the client software is set to be in an abnormal state, and a timer is set to start timing.
Step 206: if the client software has no flash back problem before the timed time reaches the preset time, setting the flash back state information of the client software to be in a non-flash back state when the timed time reaches the preset time, and ending the operation;
further, if the client software has not a flash back problem before the timed time reaches the preset time, the running state information of the client software is set to be in a normal state when the timed time reaches the preset time.
If the client software has the flash quit problem before the timed time exceeds the preset time, all operations are finished, correspondingly, the flash quit state information of the client software is in a flash quit state, namely the flash quit problem of the client software during the starting operation is recorded, and the operation state information is in an abnormal state, so that technicians can determine that the flash quit problem of the client software during the starting operation is caused within the preset time.
Step 207: and repairing the client software, and starting the client software after repairing, so that the normal operation of the client software is ensured, and the operation is finished.
Specifically, the client software can be repaired by two methods, including:
firstly, downloading the client software of the latest version, installing the client software of the latest version, repairing the client software, and starting the client software of the latest version after installing the client software of the latest version.
The download address of the client software can be stored in advance, specifically, the download address of the client software is obtained, the latest version of the client software is downloaded according to the download address of the client software, the latest version of the client software is installed after the downloading is completed, and the latest version of the client software is started after the latest version of the client software is installed.
The client software is continuously started and operated to generate the flash back problem, and the flash back problem can be solved in the client software with the latest version by technicians, so that the client software with the latest version is downloaded and installed, the client software with the latest version is repaired, and the normal starting and operation of the client software can be ensured.
And secondly, locally acquiring a data directory corresponding to the client software at the terminal, deleting the acquired data directory, starting the client software to create the data directory after the client software is started, and enabling the client software to acquire and load the user data into the created data directory, so that the user data of the client software is repaired, and the client software is ensured to be normally started and run.
After deleting the data directory of the client software and starting the client software, if the client software finds that the corresponding data directory does not exist locally, the client software automatically creates the data directory, acquires the user data corresponding to the client software from the network, and then loads the acquired user data into the created data directory, so that the user data corresponding to the client software can be repaired, and the client software is ensured to be started and operated normally.
The reason for the problem of the flash back of the client software may be that the user data corresponding to the client is damaged, so that the user data of the client software locally stored in the terminal is deleted, and then the user data of the client software is reloaded, so that the damaged user data can be repaired, and the normal operation of the client software is ensured.
Further, when the client software is repaired, the number of times of flash back of the client software is cleared.
After the client software is repaired and started, the information of the flash back state of the client software is set to be the flash back state, and the execution is started from step 204.
Further, after the client software is repaired, reporting information including the flash back state information of the client software, the operation state information of each operation included in the client software and the running state information of the client software may be sent to an administrator.
Further, the reported information may also include information such as the user name and the latest time when the client software was last started.
In the embodiment of the invention, when the client software needs to be started and operated, the flash back state information of the client software is judged, if the flash back state information is in a flash back state, the flash back times of the client software are increased, whether the client software is available or not is determined according to the flash back times, if the client software is not available, the client software is repaired, and the client software is started after the client software is repaired. Therefore, when the client software is started and operated continuously for multiple times and has the problem of flash back, the client software is determined to be unavailable, and then the client software is repaired to ensure the normal operation of the client software.
Example 3
As shown in fig. 3, an embodiment of the present invention provides an apparatus for ensuring normal operation of software, including:
the judging module 301 is configured to judge the flash back state information of the client software when the client software needs to be started and run;
a determining module 302, configured to increase a number of times of flash back of the client software if the information of the flash back state is the flash back state, and determine whether the client software is available according to the number of times of flash back;
a repairing module 303, configured to repair the client software and start the client software after the repair if the determining module 302 determines that the client software is not available.
The determining module 302 is specifically configured to determine the number of times of flash back, determine that the client software is available if the number of times of flash back does not exceed a preset number of times, and determine that the client software is unavailable if the number of times of flash back exceeds the preset number of times.
Wherein, the repair module 303 includes:
the downloading unit is used for downloading the client software with the latest version, installing the client software with the latest version to realize the restoration of the client software and starting the client software with the latest version after installation; or,
and the deleting unit is used for acquiring a data directory corresponding to the client software, deleting the data directory, starting the client software, creating the data directory after the client software is started, and acquiring and loading the user data into the created data directory by the client software so as to repair the user data corresponding to the client software.
Further, if the information of the flash back status is a non-flash back status or client software is available, the apparatus further includes:
and the first setting module is used for setting the flash quit state information of the client software to be in a flash quit state, starting the client software and monitoring the client software.
Further, the apparatus further comprises:
and the timing module is used for starting timing when the client software is monitored to finish loading the main interface of the client software if the client software does not have the flash back problem before finishing loading the main interface of the client software.
Further, the apparatus further comprises:
and the second setting module is used for setting the flash quit state information of the client software into a non-flash quit state when the timed time reaches the preset time if the problem of flash quit of the client software does not occur before the timed time reaches the preset time.
Further, the apparatus further comprises:
and the third setting module is used for setting the operation state information of the operation to be in an abnormal state if the client software is monitored to operate, and setting the operation state information of the operation to be in a normal state if the client software does not have a flash back problem before the client software finishes loading the main interface of the client software.
Further, the apparatus further comprises:
and the third setting module is used for setting the running state information of the client software to be in an abnormal state when the client software is monitored to finish loading the main interface of the client software, and if the client software does not have the problem of flash back before the timed time reaches the preset time, setting the running state information of the client carbonyl software to be in a normal state when the timed time reaches the preset time.
Further, if the information of the flash back status is the non-flash back status, the apparatus further includes:
and the zero clearing module is used for clearing the flash back times of the client software.
In the embodiment of the invention, when the client software needs to be started and operated, the flash back state information of the client software is judged, if the flash back state information is in a flash back state, the flash back times of the client software are increased, whether the client software is available or not is determined according to the flash back times, if the client software is not available, the client software is repaired, and the client software is started after the client software is repaired. Therefore, when the client software is in flash back when continuously and repeatedly started to run, the client software is determined to be unavailable, and then the client software is repaired to ensure the normal running of the client software.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (16)
1. A method for ensuring proper operation of software, the method comprising:
when the client software needs to be started and operated, judging the flash back state information of the client software, wherein the flash back state information is used for recording whether the client software has a flash back problem or not when the client software is started and operated last time;
if the information of the flash quit state is the flash quit state, increasing the flash quit times of the client software, and determining whether the client software is available according to the flash quit times;
if not, repairing the client software and starting the client software after repair;
if the flash quit state information is in a non-flash quit state or the client software is available, setting the flash quit state information of the client software to be in a flash quit state, starting the client software and monitoring the client software, setting the operation state information of the software initialization operation to be in a non-normal state when monitoring that the client software carries out software initialization operation, and setting the operation state information of the software initialization operation to be in a normal state after monitoring that the software initialization operation is finished; when the client software is monitored to perform account initialization operation, setting the operation state information of the account initialization operation to be in an abnormal state, and after the account initialization operation is monitored to be completed, setting the operation state information of the account initialization operation to be in a normal state.
2. The method of claim 1, wherein said determining whether the client software is available based on the number of flash backs comprises:
and judging the flash back frequency, if the flash back frequency does not exceed the preset frequency, determining that the client software is available, and if the flash back frequency exceeds the preset frequency, determining that the client software is unavailable.
3. The method of claim 1, wherein said repairing the client software and launching the client software after repair, comprises:
downloading the client software of the latest version, installing the client software of the latest version to realize the restoration of the client software, and starting the client software of the latest version after installation; or,
the method comprises the steps of obtaining a data directory corresponding to the client software, deleting the data directory, starting the client software, creating the data directory after the client software is started, and obtaining and loading user data into the created data directory by the client software so as to repair the user data corresponding to the client software.
4. The method of claim 1, wherein the method further comprises:
and if the client software does not have the flash back problem before the client software finishes loading the main interface of the client software, starting timing when the client software finishes loading the main interface of the client software.
5. The method of claim 4, wherein the method further comprises:
and if the client software has no flash quit problem before the timed time reaches the preset time, setting the flash quit state information of the client software to be in a non-flash quit state when the timed time reaches the preset time.
6. The method of claim 1, wherein after monitoring the client software, further comprising:
if the client software is monitored to operate, the operating state information of the operation is set to be in an abnormal state, and if the client software does not have the problem of flash back before the client software finishes loading the main interface of the client software, the operating state information of the operation is set to be in a normal state when the client software finishes loading the main interface of the client software.
7. The method of claim 4, wherein the method further comprises:
and when the client software is monitored to finish loading the main interface of the client software, setting the running state information of the client software to be in an abnormal state, and if the client software does not have the problem of flash back before the timed time reaches the preset time, setting the running state information of the client carbonyl software to be in a normal state when the timed time reaches the preset time.
8. The method of claim 1, wherein before the setting the flash-back status information of the client software to a flash-back status if the flash-back status information is a non-flash-back status, further comprising:
and clearing the flash back times of the client software.
9. An apparatus for ensuring proper operation of software, the apparatus comprising:
the judging module is used for judging the flash back state information of the client software when the client software needs to be started and operated, wherein the flash back state information is used for recording whether the client software has a flash back problem when the client software is started and operated last time;
the determining module is used for increasing the flash back times of the client software if the flash back state information is in a flash back state, and determining whether the client software is available according to the flash back times;
the repair module is used for repairing the client software and starting the client software after repair if the determination module determines that the client software is unavailable;
if the flash quit state information is a non-flash quit state or the client software is available, the device is further used for setting the flash quit state information of the client software to be a flash quit state, starting the client software and monitoring the client software, setting the operation state information of the software initialization operation to be a non-normal state when the client software is monitored to perform the software initialization operation, and setting the operation state information of the software initialization operation to be a normal state after the software initialization operation is monitored; when the client software is monitored to perform account initialization operation, setting the operation state information of the account initialization operation to be in an abnormal state, and after the account initialization operation is monitored to be completed, setting the operation state information of the account initialization operation to be in a normal state.
10. The apparatus of claim 9,
the determining module is specifically configured to determine the number of times of flash back, determine that the client software is available if the number of times of flash back does not exceed a preset number of times, and determine that the client software is unavailable if the number of times of flash back exceeds the preset number of times.
11. The apparatus of claim 9, wherein the repair module comprises:
the downloading unit is used for downloading the client software of the latest version, installing the client software of the latest version to realize the restoration of the client software and starting the client software of the latest version after installation; or,
and the deleting unit is used for acquiring a data directory corresponding to the client software, deleting the data directory, starting the client software, creating the data directory after the client software is started, and acquiring and loading user data into the created data directory by the client software so as to repair the user data corresponding to the client software.
12. The apparatus of claim 9, wherein the apparatus further comprises:
and the timing module is used for starting timing when the client software is monitored to finish loading the main interface of the client software if the client software does not have the flash back problem before finishing loading the main interface of the client software.
13. The apparatus of claim 12, wherein the apparatus further comprises:
and the second setting module is used for setting the flash quit state information of the client software into a non-flash quit state when the timed time reaches the preset time if the client software does not have the flash quit problem before the timed time reaches the preset time.
14. The apparatus of claim 9, wherein the apparatus further comprises:
and the third setting module is used for setting the operating state information of the operation to be in an abnormal state if the client software is monitored to operate, and setting the operating state information of the operation to be in a normal state if the client software does not have a flash back problem before the client software finishes loading the main interface of the client software.
15. The apparatus of claim 12, wherein the apparatus further comprises:
and the third setting module is used for setting the running state information of the client software to be in an abnormal state when the client software is monitored to finish loading the main interface of the client software, and if the client software does not have the problem of flash back before the timed time reaches the preset time, setting the running state information of the client carbonyl software to be in a normal state when the timed time reaches the preset time.
16. The apparatus of claim 9, wherein if the flash back status information is a non-flash back status, the apparatus further comprises:
and the zero clearing module is used for clearing the flash back times of the client software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210148916.2A CN102681874B (en) | 2012-05-14 | 2012-05-14 | A kind ofly guarantee the method that software normally runs and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210148916.2A CN102681874B (en) | 2012-05-14 | 2012-05-14 | A kind ofly guarantee the method that software normally runs and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102681874A CN102681874A (en) | 2012-09-19 |
| CN102681874B true CN102681874B (en) | 2015-10-21 |
Family
ID=46813847
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210148916.2A Active CN102681874B (en) | 2012-05-14 | 2012-05-14 | A kind ofly guarantee the method that software normally runs and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102681874B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902399B (en) * | 2012-12-28 | 2017-05-10 | 华为技术有限公司 | Software system repair processing method and software system repair processing device |
| CN104123210B (en) * | 2013-04-26 | 2018-01-09 | 腾讯科技（深圳）有限公司 | Test the method, apparatus and system of browser performance |
| CN104182331B (en) * | 2013-05-20 | 2018-04-27 | 腾讯科技（深圳）有限公司 | Browser performance test method, system and terminal |
| CN104426947A (en) * | 2013-08-27 | 2015-03-18 | 中兴通讯股份有限公司 | Terminal intelligent updating method and system, terminal and data updating server |
| CN106020866A (en) * | 2016-05-10 | 2016-10-12 | 北京金山安全软件有限公司 | Blue screen processing method and device and terminal |
| CN107798464A (en) * | 2017-09-19 | 2018-03-13 | 上海壹账通金融科技有限公司 | Service administering method, electronic equipment and the computer-readable recording medium of client |
| CN107861830A (en) * | 2017-12-01 | 2018-03-30 | 深圳乐信软件技术有限公司 | Detection method, device, storage medium and the mobile terminal of application crash |
| CN109271269A (en) * | 2018-09-20 | 2019-01-25 | 阿里巴巴集团控股有限公司 | A kind of processing method, device and equipment that application sudden strain of a muscle is moved back |
| CN111522676B (en) * | 2020-04-01 | 2021-10-01 | 五八有限公司 | Application program repairing method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1755644A (en) * | 2004-09-30 | 2006-04-05 | 微软公司 | Method, system, and apparatus for providing customer product support for a software program based upon states of program execution instability |
| CN101201770A (en) * | 2006-12-15 | 2008-06-18 | 大唐移动通信设备有限公司 | Method and system for storing important information before system collapse |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8020149B2 (en) * | 2006-08-04 | 2011-09-13 | Apple Inc. | System and method for mitigating repeated crashes of an application resulting from supplemental code |
-
2012
- 2012-05-14 CN CN201210148916.2A patent/CN102681874B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1755644A (en) * | 2004-09-30 | 2006-04-05 | 微软公司 | Method, system, and apparatus for providing customer product support for a software program based upon states of program execution instability |
| CN101201770A (en) * | 2006-12-15 | 2008-06-18 | 大唐移动通信设备有限公司 | Method and system for storing important information before system collapse |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102681874A (en) | 2012-09-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102681874B (en) | A kind ofly guarantee the method that software normally runs and device | |
| CN107729066B (en) | Automatic construction and release method and device based on SVN (singular value decomposition) resource library | |
| CN106598835B (en) | Application testing method, device and system | |
| CN101593121B (en) | Method, device and system for software on-line upgrade | |
| EP2696532A2 (en) | Method, server and system for starting application | |
| EP2864873B1 (en) | Auto-update while running a client software application with update handshake between versions and runtime validation of the successor version | |
| CN106549789B (en) | Method and system for realizing server installation | |
| CN106201796A (en) | The collocation method of a kind of test and device | |
| CN111176669A (en) | Cloud application installation starting method, cloud streaming server and storage server | |
| CN110851081A (en) | Method and device for safely cleaning storage space and computer readable storage medium | |
| CN104572217A (en) | Updating method and system of wearable intelligent device | |
| CN108536464A (en) | A kind of hot restorative procedure and device of application program | |
| CN103840968A (en) | Version updating method, version updating device and terminal equipment | |
| CN105786636B (en) | A kind of system repair and device | |
| CN110597545A (en) | Hot patch intelligent upgrading method and system based on OTA component | |
| CN102300239B (en) | Base station and self-starting method thereof | |
| CN113157481B (en) | Cluster-based server time-hopping fault processing method, device and system | |
| EP3260981B1 (en) | Information processing apparatus, information processing system, and information processing method for updating firmware | |
| CN113515291A (en) | Equipment online upgrading method and device | |
| CN113050968B (en) | Firmware upgrading method and device | |
| CN102137129A (en) | Processing method, system and device for allocation file Profile | |
| CN109254782B (en) | Operating system installation method and device | |
| CN112214249B (en) | Cross-platform self-starting program method based on USB device | |
| CN114138312A (en) | Upgrade test method, device, electronic equipment and computer readable storage medium | |
| CN103970648A (en) | Test method and system of installation package |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200825 Address after: Shenzhen Futian District City, Guangdong province 518000 Zhenxing Road, SEG Science Park 2 East Room 403 Co-patentee after: TENCENT CLOUD COMPUTING (BEIJING) Co.,Ltd. Patentee after: TENCENT TECHNOLOGY (SHENZHEN) Co.,Ltd. Address before: 518000 Guangdong city of Shenzhen province Futian District SEG Science Park 2 East Room 403 Patentee before: TENCENT TECHNOLOGY (SHENZHEN) Co.,Ltd. |
|
| TR01 | Transfer of patent right |