Browser Crash Data Filtering and Analysis System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies lack a solution for effectively collecting, storing, analyzing, and identifying browser crash information at the cloud system level, leading to inefficiencies in processing and resolving browser crashes.

Innovation Solution

A browser crash information processing system and method that involves receiving browser crash status information, generating crash identification information to determine if the browser can upload a crash data packet, analyzing the packet using an automatic analyzing program, and sending the results back to the browser, thereby enabling cloud-level collection, processing, and identification of browser crashes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the browser uploads all crash data packets without filtering, then complete crash information can be collected, but network bandwidth and server storage resources are wasted on duplicate or unnecessary crash data

Engineering Contradiction:
Improvecrash information collection completenessVSAvoidnetwork bandwidth and storage resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The server performs preliminary filtering of crash data packets before full processing. When a crash packet is received, the server first checks whether similar crash information already exists in the database. Only crash packets that represent new or distinct crash scenarios are retained for further analysis, while duplicates are filtered out beforehand. This preliminary action prevents waste of network bandwidth and storage resources on redundant data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system changes the parameter of crash data identification from uploading all raw crash packets to uploading filtered crash packets based on similarity comparison. By introducing a filtering mechanism that compares crash parameters (such as crash type, module, and stack trace) against existing records, the system transforms the data flow to only include meaningful new crash information, thereby reducing resource consumption while maintaining collection completeness.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If the server analyzes every crash data packet in detail, then accurate crash diagnosis can be achieved, but processing time and computational resources are excessively consumed

Engineering Contradiction:
Improvecrash diagnosis accuracyVSAvoidcrash processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The server performs preliminary classification of crash data packets by comparing them against existing crash databases. Crash packets that match known patterns are quickly identified and handled with standardized diagnostic procedures, while only novel or unusual crash packets undergo detailed analysis. This preliminary sorting action reduces overall processing time while maintaining diagnostic accuracy for both common and rare crash scenarios.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies partial analysis to most crash packets and excessive (full) analysis only to necessary cases. By implementing a tiered analysis approach where the majority of crash packets receive basic filtering and classification, and only a small subset requiring detailed investigation receives full computational analysis, the system achieves accurate diagnosis where needed while minimizing overall processing time and resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

3Productivity

If the system implements comprehensive filtering and analysis of crash data, then resource efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvecrash processing efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The crash processing system is segmented into distinct functional modules: a crash data reception module, a filtering and comparison module that checks against existing databases, an analysis module for detailed examination of selected packets, and a response generation module. This segmentation allows each component to perform its specific function independently, improving overall processing efficiency through specialized processing while managing complexity by organizing functions into separate, manageable units with clear interfaces.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9876696B2Method and system for processing browser crash information
Publication Date: 2018.01.23 BEIJING QIHOOD TECHNOLOGY CO LTD
  • US9876696B2 patent drawing
  • US9876696B2 patent drawing
  • US9876696B2 patent drawing

AI summary

The disclosure discloses a method and a system for processing browser crash information. The method comprises: receiving browser crash status information uploaded when a browser crashes; according to the browser crash status information, generating crash identification information to indicate whether allowing the browser to upload a crash data packet or not; feeding the crash identification information back to the browser; if the crash identification information indicates allowing the browser to upload the crash data packet, receiving crash information including the crash data packet uploaded by the browser; starting up an automatic crash data packet analyzing program to analyze the crash data packet; and sending the analyzing result of the crash data packet back to the browser uploading the crash data packet. The disclosure provides a solution at cloud system level to specifically collect, process, analyze and identify the browser crash information.