# US 2005/0240798 A1 · System and method of preventing a web browser plug-in module from generating a failure

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0240798 A1
- Document ID: US20050240798A1
- Status: Published application
- Kind: A1
- Application number: 10/814,591
- Filed: 2004-03-31
- Published: 2005-10-27
- Earliest claimed: 2004-03-31
- Assignees: Microsoft Corporation
- Inventors: Joseph Benedek; Roberto Franco; Quji Guo; J. Hally; Reid Holmes; Roman Pamucci; Edward Praitis; Christopher Sager; Brian Wentz
- Web page: https://patentgrep.com/patent/US20050240798A1

## CPC

- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present invention improves the stability of a Web browser by identifying plug-in modules that cause failures. Data in memory at the time of a failure is analyzed and a failure signature is generated. The failure signature is compared to a database of known failure signatures so that the source of the failure may be identified. If a plug-in module to a Web browser is identified as the source of a failure, options are presented to the user who may update the plug-in module with code that does not produce a failure or disable the plug-in module altogether.

## Claims

### Claim 1

In a computing device having at least one plug-in module that extends the functionality of a Web browser, a method of identifying a plug-in module that generated a failure, comprising:
in response to receiving notice of a failure, obtaining selected contents of memory of said computing device created at the time of the failure;
generating a failure signature that is characteristic of the plug-in module that generated the failure; and
comparing said failure signature with one or more failure signatures generated by known plug-in modules.

### Claim 2 (depends on 1)

The method as recited in claim 1, further comprising:
if the failure signature is characteristic of a known plug-in module, determining if the known plug-in module has an update that does not generate a failure.

### Claim 3 (depends on 2)

The method as recited in claim 2, further comprising:
if the known plug-in module has an update that does not generate failures, informing the user of the availability of the update.

### Claim 4 (depends on 1)

The method as recited in claim 1, further comprising allowing the user to disable the plug-in module that generated the failure.

### Claim 5 (depends on 1)

The method as recited in claim 1 wherein obtaining the contents in memory of said computing device at the time of the failure includes obtaining a minidump file.

### Claim 6 (depends on 1)

The method as recited in claim 1 wherein generating a failure signature from the contents of memory that is characteristic of the plug-in module that generated the failure includes:
identifying the library that was executing at the time of the failure;
determining the plug-in module that uses said library; and
identifying the application that interacts with the plug-in module that uses said library.

### Claim 7 (depends on 6)

The method as recited in claim 6 wherein identifying the library that was executing at the time of the failure includes searching a minidump file.

### Claim 8 (depends on 6)

The method as recited in claim 6 wherein determining the plug-in module that uses said library includes searching the system registry for associations between plug-in modules and libraries.

### Claim 9 (depends on 6)

The method as recited in claim 6 wherein identifying the application that interacts with the plug-in module includes searching the system registry for associations between applications and plug-in modules.

### Claim 10

A computer-readable medium bearing computer-executable instructions that, when executed, carry out a method of identifying a plug-in module that generated a failure, comprising:
in response to receiving notice of a failure, obtaining selected contents of memory of said computing device created at the time of the failure;
generating a failure signature that is characteristic of the plug-in module that generated the failure; and
comparing said failure signature with one or more failure signatures generated by known plug-in modules.

### Claim 11 (depends on 10)

The computer-readable medium as recited in claim 10, further comprising:
if the failure signature is characteristic of a browser plug-in module, determining if the known plug-in module has an update that does not generate a failure.

### Claim 12 (depends on 1)

The computer-readable medium as recited in claim 1 1, further comprising:
if the known plug-in module has an update that does not generate failures, informing the user of the availability of the update.

### Claim 13 (depends on 10)

The computer-readable medium as recited in claim 10, further comprising allowing the user to disable the plug-in module that generated the failure.

### Claim 14 (depends on 10)

The computer-readable medium as recited in claim 10 wherein obtaining the contents in memory of said computing device at the time of the failure includes obtaining a minidump file.

### Claim 15 (depends on 10)

The computer-readable medium as recited in claim 10 wherein generating a failure signature from the contents of memory that is characteristic of the plug-in module that generated the failure includes:
identifying the segment of code that was executing at the time of the failure; and
determining the library that contains said segment of code that was executing at the time of the failure; and
identifying the application that interacts with the plug-in module that uses said library.

### Claim 16 (depends on 15)

The computer-readable medium as recited in claim 15, further comprising determining if said segment of code that was executing at the time of the failure includes searching a minidump file.

### Claim 17 (depends on 16)

The computer-readable medium as recited in claim 16 wherein determining if said segment of code is from a library used by a plug-in module to a Web browser includes searching the system registry for associations between plug-in modules and libraries.

### Claim 18 (depends on 15)

The computer-readable medium as recited in claim 15 wherein identifying the segment of code that was executing at the time of the failure includes searching the system registry for associations between applications and plug-in modules.

### Claim 19

A computer-readable medium bearing computer-executable instructions which, when executed:
identifies plug-in modules used in conjunction with a Web browser;
displays a graphical user interface that lists the plug-in modules used in conjunction with a Web browser; and
supports disabling one or more of the plug-in modules used in conjunction with a Web browser.

### Claim 20 (depends on 19)

The computer-readable medium recited in claim 19 wherein identifying one or more plug-in modules used in conjunction with a Web browser includes searching the system registry for associations between plug-in modules and a Web browser.

### Claim 21 (depends on 19)

The computer-readable medium recited in claim 19 wherein the graphical user interface indicates whether each plug-in module used in conjunction with a Web browser may be updated.
