Providing a watchdog timer to enable collection of crash data

Patent metadata

Field	Value
Publication number	US-10365960-B2
Application number	US-201715617169-A
Country	US
Kind code	B2
Filing date	Jun 8, 2017
Priority date	Dec 9, 2013
Publication date	Jul 30, 2019
Grant date	Jul 30, 2019

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.

First claim

What is claimed is:

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.

Assignees

• Google Llc

Inventors

• Perry Ryan
• Seibert Jr Jeffrey Hall
• Ma Zhen
• Massicotte Matt

Classifications

• G06F11/0757

  by exceeding a time limit, i.e. time-out, e.g. watchdogs · CPC title

• G06F11/0778 Primary

  Dumping, i.e. gathering error/state information after a fault for later diagnosis · CPC title

• G06F11/0715

  in a system implementing multitasking (multitasking per se G06F9/46) · CPC title

• G06F11/0706

  the processing taking place on a specific hardware platform or in a specific software environment · CPC title

• G06F11/1441

  Resetting or repowering · CPC title