AUTOMATED CRASH RECOVERY

Number: 20220229718
Published: 2022-07-21
Filed: 2022-04-04
Assignee: Disney Enterprises, Inc.
Inventors: KAGAN; Gary, LEFLER; Nathan, PHELPS; Josh, CORRIGAN-COLVILLE; James A., MANNING; Benjamin
CPC: G06F11/0715; G06F11/0748; G06F11/0778; G06F11/079; G06F11/3636; G06F11/366
Verdict: Set aside software crash recovery, IT, unrelated
Source: Google Patents · FreePatentsOnline

Abstract

Methods for improving operation of a user device executing an application. The methods include collecting a first set of data corresponding to a run time environment of the application, collecting a second set of data corresponding to a crash of the application, identifying a cause of the crash based on the first set of data and a second set of data and determining the cause of the crash is associated with an application feature corresponding to a feature flag.

Background

BACKGROUND

An application running on a user device may crash for any of a plurality of different reasons. Under conventional circumstances, the cause of the crash may not be fixed until an update is provided to the user device. However, the process of notifying a developer that the crash has occurred, determining the cause of the crash, generating the update and providing the update to the user device takes time. The longer this process takes, the longer the user is without a properly functioning application.

Various negative consequences may arise while the cause of the crash remains unresolved. For example, the application's ability to generate revenue may be limited, the application's reputation may be negatively impacted, the user may be unable to access services the user expects to be available, the user may turn to a competitor's application, etc. Thus, both the entity that distributes the application and the user want the application to resume operating without crashing as quickly as possible. Accordingly, there is a need for a mechanism that is able to quickly mitigate the cause of the crash.

Claims

1. A method, comprising: collecting a first set of data corresponding to a run time environment of an application executing on a user device; collecting a second set of data corresponding to a crash of the application; identifying an executable portion of the application, comprising at least one of: (i) identifying a cause of the crash based on the first set of data and the second set of data, and identifying the executable portion of the application based on the cause of the crash; or (ii) determining that the cause of the crash is indeterminate, and identifying the executable portion of the application based on the first set of data; and altering execution of the identified executable portion of the application. || 8. A user device comprising: a processor; and a memory storing a program, which, when executed on the processor, performs operations, the operations comprising: collecting a first set of data corresponding to a run time environment of an application executing on a user device; collecting a second set of data corresponding to a crash of the application; identifying an executable portion of the application, comprising at least one of: (i) identifying a cause of the crash based on the first set of data and the second set of data, and identifying the executable portion of the application based on the cause of the crash; or (ii) determining that the cause of the crash is indeterminate, and identifying the executable portion of the application based on the first set of data; and altering execution of the identified executable portion of the application. || 15. A non-transitory computer-readable medium containing computer program code that, when executed by operation of one or more computer processors, performs operations comprising: collecting a first set of data corresponding to a run time environment of an application executing on a user device; collecting a second set of data corresponding to a crash of the application; identifying an executable portion of the application, comprising at least one of: (i) identifying a cause of the crash based on the first set of data and the second set of data, and identifying the executable portion of the application based on the cause of the crash; or (ii) determining that the cause of the crash is indeterminate, and identifying the executable portion of the application based on the first set of data; and altering execution of the identified executable portion of the application.