Crash data handling
AssigneeGoogle Inc.
InventorsKenneth E. Mixter, Darin S. Petkov
Life of this patent
Estimating the term…
Abstract
Systems and methods for handling a crash of a process running on an operating system (OS) of a client are provided. In some aspects, a method includes generating crash data based on a dump file associated with the crash of the process. The crash data is associated with a first user logged in to the OS at the time of the crash. The method also includes storing the crash data in a cryptographically secure location on the client such that the crash data persists across reboot of the client. The method also includes preventing the crash data from being sent to an analysis server when the first user is not logged in to the OS.
Claims28
A method for handling a crash of a process running on an operating system (OS) of a client, the method comprising:
- generating crash data based on a dump file associated with the crash of the process, wherein the crash data is associated with a first user logged into the OS at a time of the crash;
- storing the crash data in a cryptographically secure location on the client such that the crash data persists across reboot of the client;
- and
- preventing the crash data from being sent to an analysis server when the first user is not logged into the OS,
- wherein the preventing comprises placing the crash data in a queue, including items to be sent to the analysis server, only when the first user is logged into the OS.
A system for handling a crash of a process running on an operating system (OS) of a client, the system comprising:
- a processor;
- and
- a crash handler module configured to generate, via the processor, crash data based on a dump file associated with the crash of the process, the crash data being associated with a first user logged into the OS at a time of the crash,
- wherein the crash handler module is configured to store the crash data in a cryptographically secure location on the client such that the crash data persists across reboot of the client,
- wherein the crash handler module is configured to prevent the crash data from being sent to an analysis server when the first user is not logged into the OS, and
- wherein the preventing comprises placing the crash data in a queue, including items to be sent to the analysis server, only when the first user is logged into the OS.
A method for handling a crash of a process running on an operating system (OS) of a client, the method comprising:
- extracting crash data from a dump file associated with the crash of the process, wherein the crash data is associated with a first user logged into the OS at a time of the crash, wherein the crash data is extracted from the dump file such that at least one of email address information, internet protocol address information, media access control information, recent web page information, and screen capture information is excluded from the crash data, and wherein a size of the crash data is less than 1% of a size of the dump file;
- storing the crash data in a cryptographically secure location on the client such that the crash data persists across reboot of the client;
- and
- preventing the crash data from being sent to an analysis server when the first user is not logged into the OS, and when a second user different from the first user is logged into the OS and connection to the analysis server is available.
A system for handling a crash of a process running on an operating system (OS) of a client, the system comprising:
- a processor;
- and
- a crash handler module configured to generate, via the processor, crash data based on a dump file associated with the crash of the process, the crash data being associated with a first user logged into the OS at a time of the crash, a size of the crash data being less than 1% of a size of the dump file,
- wherein the crash handler module is configured to store the crash data in a cryptographically secure location on the client such that the crash data persists across reboot of the client, and
- wherein the crash handler module is configured to prevent the crash data from being sent to an analysis server when the first user is not logged into the OS.
A non-transitory machine-readable medium encoded with instructions for a method of handling a crash of a process running on an operating system (OS) of a client, the method comprising:
- generating crash data based on a dump file associated with the crash of the process, wherein the crash data is associated with a first user logged into the OS at a time of the crash, and wherein a size of the crash data is less than 1% of a size of the dump file;
- storing the crash data in a cryptographically secure location on the client such that the crash data persists across reboot of the client;
- and
- preventing the crash data from being sent to an analysis server when the first user is not logged into the OS.
A non-transitory machine-readable medium encoded with instructions for a method of handling a crash of a process running on an operating system (OS) of a client, the method comprising:
- generating crash data based on a dump file associated with the crash of the process, wherein the crash data is associated with a first user logged into the OS at the time of the crash;
- storing the crash data in a cryptographically secure location on the client such that the crash data persists across reboot of the client;
- and
- preventing the crash data from being sent to an analysis server when the first user is not logged into the OS,
- wherein the preventing comprises placing the crash data in a queue, including items to be sent to the analysis server, only when the first user is logged into the OS.
Dependencies are inferred from the claim text.