System and method for detection of, prevention of, and recovery from software execution failure

Patent metadata

Field	Value
Publication number	US-11113147-B2
Application number	US-202017060462-A
Country	US
Kind code	B2
Filing date	Oct 1, 2020
Priority date	Apr 27, 2018
Publication date	Sep 7, 2021
Grant date	Sep 7, 2021

Abstract

Systems and methods are disclosed herein for monitoring, detecting, and mitigating hardware and software failures. An error detection module monitors the execution of software processes and detects failures of the monitored processes. The error detection module may monitor reboot events and correlate reboot events with failures of the monitored software processes. If a monitored process fails, the error detection module may log the failure and its cause. If the same process has failed numerous times, causing the user device to experience a reboot loop, remedial action may be taken based on the cause of the failure.

First claim

What is claimed is:

1. A method for handling software execution failures on a user device, the method comprising:
monitoring execution of a software process on the user device;

detecting a reboot of the user device;
determining whether the reboot was caused by a prerequisite process not having been completed; and
in response to determining that the cause of the reboot is a prerequisite process not having been completed, slowing a speed at which the software process is executed to allow the prerequisite process to complete prior to execution of the software process.

2. The method of claim 1 , further comprising:
incrementing a counter; and
determining whether the value of the counter exceeds a failure threshold;
wherein slowing the speed at which the software process is executed occurs further in response to determining that the value of the counter exceeds the failure threshold.

3. The method of claim 2 , wherein the counter is a reboot counter.

4. The method of claim 2 , wherein the counter is one of a plurality of counters, each counter being associated with a respective cause of a reboot, and wherein incrementing the counter further comprises identifying a respective counter of the plurality of counters associated with the prerequisite process.

5. The method of claim 1 , further comprising:
detecting, within a threshold period of time after the reboot, a second reboot of the user device;
determining whether the second reboot was also caused by the prerequisite process not having been completed.

6. The method of claim 5 , further comprising:
executing a limited boot process; and
transmitting, to a server, a request for a software update.

7. The method of claim 1 , wherein the software process comprises a plurality of steps, and wherein slowing the speed at which the software process is executed comprises pausing execution of the software process for a period of time after each step.

8. The method of claim 1 , wherein the software process comprises a plurality of steps, the method further comprising:
identifying a step of the plurality of steps at which the reboot occurred; and
monitoring execution of the prerequisite process;
wherein slowing the speed at which the software process is executed comprises preventing execution of the identified step until the prerequisite process has been completed.

9. The method of claim 1 , wherein the software process stores status information related to the execution and failure of the software process in a data structure.

10. The method of claim 9 , wherein determining the cause of the reboot further comprises:
determining a time at which the reboot occurred;
accessing the data structure;
determining status information having a timestamp at or near the determined time at which the reboot occurred;
and determining, based on the status information, the cause of the reboot.

11. A system for handling software execution failures on a user device, the system comprising:
memory; and
control circuitry configured to:
monitor execution of a software process on the user device;

detect a reboot of the user device;
determine whether the reboot was caused by a prerequisite process not having been completed; and
in response to determining that the cause of the reboot is a prerequisite process not having been completed, slow a speed at which the software process is executed to allow the prerequisite process to complete prior to execution of the software process.

12. The system of claim 11 , wherein the control circuitry is further configured to:
increment a counter; and
determine whether the value of the counter exceeds a failure threshold;
slow the speed at which the software process in response to determining that the value of the counter exceeds the failure threshold.

13. The system of claim 12 , wherein the counter is a reboot counter.

14. The system of claim 12 , wherein the counter is one of a plurality of counters, each counter being associated with a respective cause of a reboot, and wherein the control circuitry configured to increment the counter is further configured to identify a respective counter of the plurality of counters associated with the prerequisite process.

15. The system of claim 11 , wherein the control circuitry is further configured to:
detect, within a threshold period of time after the reboot, a second reboot of the user device;
determine whether the second reboot was also caused by the prerequisite process not having been completed.

16. The system of claim 15 , wherein the control circuitry is further configured to:
execute a limited boot process; and
transmit, to a server, a request for a software update.

17. The system of claim 15 , wherein the software process comprises a plurality of steps, and wherein the control circuitry configured to slow the speed at which the software process is executed is further configured to pause execution of the software process for a period of time after each step.

18. The system of claim 15 , wherein the software process comprises a plurality of steps, and wherein the control circuitry is further configured to:
identify a step of the plurality of steps at which the reboot occurred;
monitor execution of the prerequisite process; and
slow the speed at which the software process is executed by preventing execution of the identified step until the prerequisite process has been completed.

19. The system of claim 15 , wherein the software process stores, in the memory, status information related to the execution and failure of the software process in a data structure.

20. The system of claim 19 , wherein the control circuitry configured to determine the cause of the reboot is further configured to:
determine a time at which the reboot occurred;
access, from the memory, the data structure;
determine status information having a timestamp at or near the determined time at which the reboot occurred;
and determine, based on the status information, the cause of the reboot.

Assignees

• Rovi Guides Inc

Inventors

• Kulick Todd
• Pichkov Igor

Classifications

• G06F11/076 Primary

  by exceeding a count or rate limit, e.g. word- or bit count limit · CPC title

• G06F11/302

  where the computing system component is a software system · CPC title

• G06F11/1417 Primary

  Boot up procedures · CPC title

• G06F11/0793

  Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40) · CPC title

• G06F11/079

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title