Providing a watchdog timer to enable collection of crash data

• US 10,365,960 B2
• Filed: 06/08/2017
• Issued: 07/30/2019
• Est. Priority Date: 12/09/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Perry, Ryan, Seibert, Jr., Jeffrey Hall, Ma, Zhen, Massicotte, Matt
• Primary Examiner(s): Mccarthy, Christopher S
• Application Number:
  US15/617,169
• Publication Number:
  US 20170269987A1
• Time in Patent Office: 782 Days
• CPC Class Codes: G06F 11/0706 the processing taking place on a specific hardware platform or in a specific software environment
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/0757 by exceeding a time limit, i.e. time-out, e.g. watchdogs
• CPC Class Codes: G06F 11/0778 Dumping, i.e. gathering error/state information after a fault for later diagnosis
• CPC Class Codes: G06F 11/0787 Storage of error reports, e.g. persistent data storage, storage using memory protection
• CPC Class Codes: G06F 11/1402 Saving, restoring, recovering or retrying
• CPC Class Codes: G06F 11/1415 at system level
• CPC Class Codes: G06F 11/1441 Resetting or repowering

Abstract

A system and method for providing a watchdog timer to enable collection of crash data is provided. Upon execution of certain operations, a source thread of an application initiates a watchdog thread that periodically sample state of data relating to the application. Should the operation not complete within a watchdog timeout period, the watchdog thread invokes a crash function to collect additional state data. At least a portion of the state data is stored for later analysis and debugging.

Claims

1. A computer-implemented method comprising:

after a native application begins a particular operation, initiating a request to receive an indication in response to the particular operation being completed;

periodically sampling application state data unless or until the indication is received;

determining an amount of time that the operation system is to allow for the particular operation to be performed by the native application before the operating system designates the native application has having crashed based on stored sampled application state data in crash data; and

after the determined amount of time that an operating system is to allow for the particular operation to be performed by the native application before the operating system designates the native application as having crashed has elapsed, storing at least a portion of the sampled application state data as the crash data, then terminating the native application.

2. The computer-implemented method of claim 1, further comprising:

generating a first thread in response to the native application beginning the particular operation.

3. The computer-implemented method of claim 2, further comprising:

determining a timeout period less than the amount of time that the operating system allows for the particular operation to be performed; and

in response to the timeout period elapsing, monitoring, by the first thread, the timeout period before indicating a crash of the particular operation.

4. The computer-implemented method of claim 3, further comprising:

transmitting a message to a second thread to indicate that the timeout period is about to expire in response to the amount of time having elapsed to a predefined threshold that is less than the timeout period.

5. The computer-implemented method of claim 2, further comprising:

transmitting a locking request with the request to receive the indication to guarantee the indication will be received regardless of the native application having crashed.

6. The computer-implemented method of claim 1, further comprising:

determining an existence of the crash data in response to determining the amount of time that the operation system allows for the particular operation to be performed by the native application before the operating system designates the native application as having crashed has elapsed.

7. A system comprising:

one or more computers and one or more storage devices storing instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising;

after a native application begins a particular operation, initiating a request to receive an indication in response to the particular operation being completed;

periodically sampling application state data unless or until the indication is received;

determining an amount of time that the operation system is to allow for the particular operation to be performed by the native application before the operating system designates the native application has having crashed based on stored sampled application state data in crash data; and

after the determined amount of time that an operating system is to allow for the particular operation to be performed by the native application before the operating system designates the native application as having crashed has elapsed, storing at least a portion of the sampled application state data as the crash data, then terminating the native application.

8. The system of claim 7, wherein the operations further comprise:

generating a first thread in response to the native application beginning the particular operation.

9. The system of claim 8, wherein the operations further comprise:

determining a timeout period less than the amount of time that the operating system allows for the particular operation to be performed; and

in response to the timeout period elapsing, monitoring, by the first thread, the timeout period before indicating a crash of the particular operation.

10. The system of claim 9, wherein the operations further comprise:

transmitting a message to a second thread to indicate that the timeout period is about to expire in response to the amount of time having elapsed to a predefined threshold that is less than the timeout period.

11. The system of claim 8, wherein the operations further comprise:

transmitting a locking request with the request to receive the indication to guarantee the indication will be received regardless of the native application having crashed.

12. The system of claim 7, wherein the operations further comprise:

determining an existence of the crash data in response to determining the amount of time that the operation system allows for the particular operation to be performed by the native application before the operating system designates the native application as having crashed has elapsed.

13. A non-transitory computer-readable medium storing software comprising instructions executable by one or more computers which, upon such execution, cause the one or more computers to perform operations comprising:

after a native application begins a particular operation, initiating a request to receive an indication in response to the particular operation being completed;

periodically sampling application state data unless or until the indication is received;

determining an amount of time that the operation system is to allow for the particular operation to be performed by the native application before the operating system designates the native application has having crashed based on stored sampled application state data in crash data; and

after the determined amount of time that an operating system is to allow for the particular operation to be performed by the native application before the operating system designates the native application as having crashed has elapsed, storing at least a portion of the sampled application state data as the crash data, then terminating the native application.

14. The computer-readable medium of claim 13, wherein the operations further comprise:

generating a first thread in response to the native application beginning the particular operation.

15. The computer-readable medium of claim 14, wherein the operations further comprise:

determining a timeout period less than the amount of time that the operating system allows for the particular operation to be performed; and

in response to the timeout period elapsing, monitoring, by the first thread, the timeout period before indicating a crash of the particular operation.

16. The computer-readable medium of claim 14, wherein the operations further comprise:

transmitting a locking request with the request to receive the indication to guarantee the indication will be received regardless of the native application having crashed.

17. The computer-readable medium of claim 13, wherein the operations further comprise:

determining an existence of the crash data in response to determining the amount of time that the operation system allows for the particular operation to be performed by the native application before the operating system designates the native application as having crashed has elapsed.