Client Error Management System for Automated Crash Data Collection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current online service systems face challenges in effectively collecting and managing errors that occur in client applications, particularly due to diversified hardware and operating systems, making it difficult for developers to detect and reproduce errors without user reports and accurate client terminal environment information.

Innovation Solution

An error management system and method that intercepts events, collects error information and crash dump files when a client application crashes, and transmits them via a network in a predetermined format, allowing for centralized storage and analysis on an independent error collecting server, which provides debugging information using inverse-indexed object files and functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If error information is collected manually through user reports, then user intervention is required, but error collection efficiency is low and time-consuming

Engineering Contradiction:
Improveerror collection efficiencyVSAvoiduser intervention requirement
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The client terminal automatically collects error information and crash dump files without user intervention. The error processing module detects errors, gathers relevant data, and transmits it to the error collecting server autonomously, eliminating the need for users to manually report errors through bulletin boards or emails.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system prepares error collection mechanisms in advance by installing the error processing module in the client terminal before errors occur. This module is pre-configured to intercept events, collect error information, and transmit data automatically when errors happen, rather than waiting for user reports.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If error information is transmitted immediately when errors occur, then real-time error detection is achieved, but network stability and data transmission reliability may be compromised

Engineering Contradiction:
Improveerror detection accuracyVSAvoiddata transmission stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The system collects and stores error information locally in the client terminal before transmission. This preliminary collection ensures that error data is captured accurately at the moment of occurrence, and the stored information can be transmitted later when network conditions are favorable, balancing detection accuracy with transmission stability.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If detailed error information and crash dump files are collected, then debugging capability is improved, but data transmission volume and processing complexity increase

Engineering Contradiction:
Improveerror information detailVSAvoiddata processing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system extracts only the essential error information and relevant crash dump files that are necessary for debugging, rather than collecting all possible data. The error processing module identifies and gathers specific data elements such as error codes, timestamps, and minimal required system state information, reducing processing complexity while maintaining debugging effectiveness.

Inventive Principle:
Principle #2Taking out (Extraction)

4Ease of manufacture

If an independent error collecting server is used, then error management is centralized and improved, but system complexity increases

Engineering Contradiction:
Improveerror management centralizationVSAvoidsystem architecture complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The independent error collecting server acts as an intermediary between client terminals and the online service server. It receives error information from multiple clients, stores crash dump files, and provides debugging support without requiring direct integration with the main service server, thus centralizing error management while maintaining system modularity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7702959B2Error management system and method of using the same
Publication Date: 2010.04.20 NHN ENTERTAINMENT
  • US7702959B2 patent drawing
  • US7702959B2 patent drawing
  • US7702959B2 patent drawing

AI summary

An error management system for managing an error occurring in a client application includes: a client terminal which intercepts an event, and collects error information and a crash dump file when the client application is abnormally terminated, and transmits the collected error information and the crash dump file in a predetermined format via a network; and an error collecting server which receives the error information and the crash dump file from the client terminal, and stores the received error information and the crash dump file for each online service, the error collecting server being independent from an online service server that executes a server application providing a service in correspondence to the client application.