Microsoft Technology Licensing, LLC

Marius Cristian Constantin

Ricardo Soares Stern

Angel Monterrubio

Olga Ryabchenkova

Jason T Creighton

Jeremy Littel

Jeffrey J Wall

Somanath Krishnaswamy

Ian S Petersen

Joyce Kuo

Kent C Mai

Vallabh Patade

Ping Zhang

A server implementing a service receives a request from a client computing system and stores the request in a cache, along with a correlation identifier. The server returns a response to the request, along with a correlation identifier (ID). When a trigger input is received, indicating that a problem has been encountered at the client computing system, a diagnostic data generation system on the service accesses the cache and generates diagnostic data for the request corresponding to the correlation ID. The diagnostic data corresponding the correlation ID is then provided to a support data storage system where it can be combined with diagnostic data from the client computing system, to be accessed by a support computing system. This reduces consumption of computing resources, such as processing time, memory initialization and/or network bandwidth.

Triggering diagnostic data generation and aggregation across multiple systems to reduce computing resources

A server implementing a service receives a request from a client computing system and stores the request in a cache, along with a correlation identifier. The server returns a response to the request, along with a correlation identifier (ID). When a trigger input is received, indicating that a problem has been encountered at the client computing system, a diagnostic data generation system on the service accesses the cache and generates diagnostic data for the request corresponding to the correlation ID. The diagnostic data corresponding the correlation ID is then provided to a support data storage system where it can be combined with diagnostic data from the client computing system, to be accessed by a support computing system. This reduces consumption of computing resources, such as processing time, memory utilization and/or network bandwidth.

Systems and methods for controlling an intentional crash of a software application. One system includes a computing device including an electronic processor. The electronic processor is configured to receive a crash setting for the software application from a configuration server. The crash setting has a first value or a second value. The electronic processor is also configured to detect an unexpected use of the software application during execution. The electronic processor is configured to, in response to detecting the unexpected use and the crash setting having the first value, intentionally crash the software application causing a generation of a crash report describing a state of the software application when the unexpected use occurred. The electronic processor is configured to, in response detecting the unexpected use and the crash setting having the second value, not intentionally crash the software application.

Conditionally crashing software applications to track software use

Growing community of inventors

Redmond, WA, United States of America

Marius Cristian Constantin