Display Daemon and Render Thread Exception Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current display systems in intelligent terminals lack a monitoring and repair mechanism for the display daemon and render thread, leading to inefficient handling of refresh and display exceptions, such as crashes or stalling, which results in a poor user experience due to frozen screens.
Innovation Solution
A method is introduced to detect exceptions in the render thread and display daemon by measuring communication and processing durations, with corresponding repair policies to restart the threads or daemons, ensuring timely refresh and display operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the display system performs refresh operations without a monitoring mechanism, then the display system operates with simpler structure, but exceptions such as crashes or stalling cannot be detected, leading to frozen screens and poor user experience
Solution Approach 1:
The patent applies preliminary action by starting timers before the render thread transfers refresh requests to the display daemon and before the display daemon processes requests. This allows the system to pre-establish monitoring mechanisms that automatically detect exceptions when time thresholds are exceeded, enabling exception detection without adding complex post-processing monitoring structures.
Solution Approach 2:
The patent implements feedback by continuously monitoring communication duration and processing duration, comparing these measurements against time thresholds, and triggering exception detection when thresholds are exceeded. This feedback mechanism enables the system to automatically identify and respond to render thread and display daemon exceptions through timed measurements.
2Measurement precision
If the system monitors communication duration between render thread and display daemon, then exception detection accuracy improves, but the system requires additional timing measurements and threshold comparisons
Solution Approach 1:
The system applies preliminary action by pre-defining time thresholds for communication duration and processing duration before monitoring begins. These thresholds serve as predetermined criteria that simplify the monitoring process, allowing the system to detect exceptions through straightforward time comparisons rather than complex analysis algorithms.
Solution Approach 2:
The patent uses parameter changes by measuring time duration as a key parameter for exception detection. By monitoring communication duration and processing duration against time thresholds, the system transforms complex exception detection into a simple parameter comparison task, improving measurement precision while maintaining monitoring simplicity.
3Reliability
If the system implements repair policies to restart threads or daemons, then system reliability and display fluency improve, but the system requires additional repair logic and restart mechanisms
Solution Approach 1:
The patent applies self-service by implementing automatic repair policies that restart the render thread or display daemon when exceptions are detected through time threshold monitoring. The system serves itself by automatically identifying exceptions through duration measurements and executing repair actions without requiring external intervention or complex diagnostic procedures.
Solution Approach 2:
The system uses preliminary action by pre-establishing repair policies that are triggered when time thresholds are exceeded. These policies are prepared in advance and automatically executed upon exception detection, enabling reliable repair while maintaining simple implementation through predetermined response actions.
4Reliability
If the system measures communication and processing durations continuously, then refresh and display exception detection improves, but energy consumption increases due to continuous timing operations
Solution Approach 1:
The patent applies periodic action by measuring communication duration and processing duration at specific intervals corresponding to refresh requests, rather than continuously monitoring all system operations. The timers are started and stopped periodically with each refresh cycle, reducing energy consumption while maintaining reliable exception detection at critical moments.
Solution Approach 2:
The system uses preliminary action by pre-defining time thresholds that determine when exceptions occur. This allows the system to use simple time comparisons rather than continuous complex analysis, reducing computational energy requirements while maintaining reliable detection of refresh and display exceptions.
Data Source
Figure 1A~1B
Figure 1C
Figure 1D
AI summary
Embodiments of this application provide a method for processing refresh and display exceptions, to process refresh and display exceptions, and detect a crash cause of an application and a system in a targeted manner, thereby improving efficiency of processing refresh and display exceptions. The method includes: obtaining a refresh request of an application, where the refresh request is used to instruct to refresh display data of the application; transferring the refresh request to a display daemon by using a render thread of the application; when communication duration between the render thread and the display daemon is greater than a first time threshold, determining that an exception occurs in the render thread; and when duration in which the display daemon processes the refresh request is greater than a second time threshold, determining that an exception occurs in the display daemon.