Movatterモバイル変換


[0]ホーム

URL:


CN118193321B - Crash event monitoring method, system, vehicle and storage medium - Google Patents

Crash event monitoring method, system, vehicle and storage medium
Download PDF

Info

Publication number
CN118193321B
CN118193321BCN202410379688.2ACN202410379688ACN118193321BCN 118193321 BCN118193321 BCN 118193321BCN 202410379688 ACN202410379688 ACN 202410379688ACN 118193321 BCN118193321 BCN 118193321B
Authority
CN
China
Prior art keywords
breakdown
style
interface
pattern
collapse
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202410379688.2A
Other languages
Chinese (zh)
Other versions
CN118193321A (en
Inventor
李洪
于红超
徐开庭
赵国志
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chongqing Selis Phoenix Intelligent Innovation Technology Co ltd
Original Assignee
Chongqing Selis Phoenix Intelligent Innovation Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Chongqing Selis Phoenix Intelligent Innovation Technology Co ltdfiledCriticalChongqing Selis Phoenix Intelligent Innovation Technology Co ltd
Priority to CN202410379688.2ApriorityCriticalpatent/CN118193321B/en
Publication of CN118193321ApublicationCriticalpatent/CN118193321A/en
Application grantedgrantedCritical
Publication of CN118193321BpublicationCriticalpatent/CN118193321B/en
Activelegal-statusCriticalCurrent
Anticipated expirationlegal-statusCritical

Links

Classifications

Landscapes

Abstract

The application provides a crash event monitoring method, a crash event monitoring system, a vehicle and a storage medium, wherein the crash event monitoring method comprises the following steps: acquiring a screen capturing picture of a display interface in a target system; judging whether the screen capturing picture contains a preset interface style, wherein the type of the interface style is any one of a color style, a pattern style and a text style, and setting different sub styles based on the collapse type of the target system; if the screen capturing picture comprises the interface style, determining that the screen capturing picture is a breakdown display interface, and determining that a breakdown event occurs in the target system, wherein the breakdown display interface displays breakdown information. When a breakdown event occurs in the target system, the automatic monitoring of the breakdown event is realized, the rapid and visual perception of the breakdown event is realized, and the efficient and accurate breakdown repair can be further performed based on the screen capturing picture.

Description

Crash event monitoring method, system, vehicle and storage medium
Technical Field
The present application relates to the field of crash monitoring technologies, and in particular, to a crash event monitoring method, system, vehicle, and storage medium.
Background
During operation of the vehicle system, the system and its various services or applications may experience certain errors or anomalies to Crash, such as Java Crash, NATIVE CRASH, ANR (Application Not Responding, application unresponsiveness), due to its complexity and application code quality. Based on the characteristics that program crashes have multiple scenes and sporadic, the system is not easy to reproduce artificially, so that when the system crashes, the system is difficult to locate at a specific error position, and the situation that a tester or a developer does not know in time can occur, thereby causing hidden danger to the stability of the system and further reducing the safety performance of the whole vehicle.
In the related technology, when a system detects a crash behavior, information during the crash is generally written into logs, and the information is scattered into Log Files (Log logs), tombstone logs, dropbox (multi-box) and ANR logs, and crash repair is performed based on the logs, but because background application and service cannot be visually perceived during the crash, development and testing personnel cannot be timely perceived about the occurrence of a crash event, and key crash information is difficult to obtain from massive Log Files, so that the repair of the crash problem is not timely.
Disclosure of Invention
The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed embodiments. This summary is not an extensive overview, and is intended to neither identify key/critical elements nor delineate the scope of such embodiments, but is intended as a prelude to the more detailed description that follows.
In view of the above drawbacks of the prior art, the present application discloses a crash event monitoring method, a system, a vehicle and a storage medium, which are used for solving the technical problems that a crash event of a system cannot be known in time and cannot be repaired in time in the prior art.
In a first aspect, the present application provides a crash event monitoring method, the method comprising: acquiring a screen capturing picture of a display interface in a target system; judging whether the screen capturing picture contains a preset interface style, wherein the type of the interface style is any one of a color style, a pattern style and a text style, and setting different sub styles based on the collapse type of the target system; if the screen capturing picture comprises the interface style, determining that the screen capturing picture is a breakdown display interface, and determining that a breakdown event occurs in the target system, wherein the breakdown display interface displays breakdown information.
In an embodiment of the present application, the determining whether the screenshot includes a preset interface style includes: performing color matching, pattern matching and text matching on the screen capturing picture corresponding to a preset color pattern, a preset pattern and a preset text pattern respectively to obtain a matching result; if the matching result is that the screen capturing picture is not matched with the preset color pattern, the preset pattern and the preset text pattern, judging that the screen capturing picture does not contain the interface pattern; and if the matching result is that the screen capturing picture is matched with any one of the preset color pattern, the preset pattern and the preset text pattern, judging that the screen capturing picture contains the interface pattern.
In an embodiment of the present application, the matching of the color patterns includes: calibrating a first target pixel point in the screen capturing picture according to a preset pixel point position, wherein the first target pixel point is at least one; acquiring a first pixel value of the first target pixel point, and comparing the first pixel value with a preset pixel range once; if the first pixel value is within the pixel range, the screen capturing picture is matched with the preset color pattern; and if the first pixel value is not in the pixel range, the screen capturing picture is not matched with the preset color pattern.
In an embodiment of the present application, after the determining that the first pixel value is within the pixel range, the method further includes: calibrating the neighborhood pixel points of the first target pixel points to obtain a plurality of second target pixel points; obtaining a second pixel value of each second target pixel point, and carrying out secondary comparison on each second pixel value and the pixel range; if each second pixel value is in the pixel range, matching the screen capturing picture with the preset color pattern; if any second pixel value is not in the pixel range, the screen capturing picture is not matched with the preset color pattern.
In an embodiment of the present application, before the capturing a screen shot of a display interface in the target system, the method further includes: configuring a display function of the collapse display interface, wherein the display function comprises the interface style and the collapse information; if an operation instruction for starting the display function is received, enabling the display function to be in a starting state so as to monitor the running state of the target system.
In an embodiment of the present application, before the capturing a screen shot of a display interface in the target system, the method further includes: monitoring the operation information of the target system, and judging the system operation state and the program operation state according to the operation information; if the system running state is a breakdown state, determining that the breakdown type is a system breakdown; if the program running state is a crashed state, determining that the crashed type is program crashed; generating the crash information according to the system operation information or the program operation information; generating a display instruction of the interface style according to the collapse type and the collapse information; switching a working thread into a main thread, and responding to the display instruction, and controlling the display interface to pop up the collapse display interface.
In an embodiment of the present application, the display instruction carries a display duration, and the screenshot is intercepted based on a preset time interval, where the display duration is longer than the time interval.
In an embodiment of the present application, the setting of the interface style includes: if the interface style is a color style, setting the interface style as a first color sub-style when the collapse type is system collapse, and setting the interface style as a second color sub-style when the collapse type is program collapse; if the interface style is a pattern style, setting the interface style as a first pattern sub-style when the collapse type is system collapse, and setting the interface style as a second pattern sub-style when the collapse type is program collapse; if the interface style is a text style, setting the interface style as a first text sub-style when the collapse type is system collapse, and setting the interface style as a second text sub-style when the collapse type is program collapse.
In an embodiment of the present application, after the determining that the target system has a crash event, the method includes: determining a target collapse type according to the interface style; when the target breakdown type is system breakdown, analyzing the breakdown information according to a system breakdown repairing program to generate a first breakdown repairing scheme, wherein the breakdown information at least comprises a system memory state, running process information and driver information; when the target breakdown type is program breakdown, analyzing the breakdown information according to a program breakdown repairing program to generate a second breakdown repairing scheme, wherein the breakdown information at least comprises a package name, a process name, running time and an error call stack of the breakdown program.
In a second aspect, the present application provides a crash event monitoring system, the system comprising: the acquisition module is used for acquiring a screen capturing picture of a display interface in the target system; the judging module is used for judging whether the screen capturing picture contains a preset interface style, wherein the type of the interface style is any one of a color style, a pattern style and a text style, and different sub styles are set based on the collapse type of the target system; and the determining module is used for determining that the screen capturing picture is a breakdown display interface and determining that the target system has a breakdown event if the screen capturing picture contains the interface pattern, wherein the breakdown display interface displays breakdown information.
In a third aspect, the present application provides a vehicle characterised in that a crash event monitoring method as described in the first aspect is used, or in that a crash event monitoring system as described in the second aspect is included.
In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to perform the crash event monitoring method described in the first aspect.
As described above, the crash event monitoring method, system, vehicle and storage medium provided by the embodiments of the present application have the following beneficial effects:
Firstly, acquiring a screen capture picture of a display interface in a target system, then judging whether the screen capture picture contains a preset interface pattern, wherein the type of the interface pattern is any one of a color pattern, a pattern and a text pattern, setting different sub-patterns based on the collapse type of the target system, and finally, if the screen capture picture contains the interface pattern, determining that the screen capture picture is a collapse display interface and determining that a collapse event occurs in the target system, wherein the collapse display interface displays collapse information. In this way, when a breakdown event occurs in the target system, firstly, according to the interface style contained in the screen capturing picture, the automatic monitoring of the breakdown event and the efficient judgment of the breakdown event occurring in the target system are realized, so that a worker can timely and intuitively know the occurrence of the breakdown event; secondly, based on different sub-patterns in the screen capturing picture, the high-efficiency positioning of the breakdown type of the target system is realized; third, based on the crash display interface, reliable crash types and crash information corresponding to the crash types are provided, and efficient and accurate repair of crash events can be further promoted.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is evident that the drawings in the following description are only some embodiments of the present application and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:
FIG. 1 is a schematic diagram of an implementation environment of a crash event monitoring system according to an exemplary embodiment of the application;
FIG. 2 is a flow chart of a crash event monitoring method according to an exemplary embodiment of the application;
FIG. 3 is a schematic diagram of a display function opening and closing interface shown in an exemplary embodiment of the present application;
FIG. 4 is a schematic diagram of a crash display interface shown in accordance with an exemplary embodiment of the application;
FIG. 5 is a schematic diagram of a calibration target pixel point, according to an exemplary embodiment of the application;
FIG. 6 is a schematic diagram of a domain pixel shown in an exemplary embodiment of the application;
FIG. 7 is a flow chart illustrating another crash event monitoring method in accordance with an exemplary embodiment of the application;
FIG. 8 is a block diagram of a crash event monitoring system, shown in accordance with an exemplary embodiment of the application.
Detailed Description
Further advantages and effects of the present application will become readily apparent to those skilled in the art from the disclosure herein, by referring to the accompanying drawings and the preferred embodiments. The application may be practiced or carried out in other embodiments that depart from the specific details, and the details of the present description may be modified or varied from the spirit and scope of the present application. It should be understood that the preferred embodiments are presented by way of illustration only and not by way of limitation.
It should be noted that the illustrations provided in the following embodiments merely illustrate the basic concept of the present application by way of illustration, and only the components related to the present application are shown in the drawings and are not drawn according to the number, shape and size of the components in actual implementation, and the form, number and proportion of the components in actual implementation may be arbitrarily changed, and the layout of the components may be more complicated.
In the following description, numerous details are set forth in order to provide a more thorough explanation of embodiments of the present application, it will be apparent, however, to one skilled in the art that embodiments of the present application may be practiced without these specific details, in other embodiments, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the embodiments of the present application.
When a crash event occurs in the target system, related information during the crash is generally written into a Log, and the information is dispersed into Log, tombstone Log, dropbox and ANR Log, so that crash repair is performed based on the Log. However, the research of the inventor discovers that the background application and the service cannot be intuitively perceived when crashing, development and testing personnel cannot timely perceive the occurrence of a crash event, and key crash information is difficult to obtain from a massive log file, so that the crash problem is not timely repaired.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an implementation environment of a crash event monitoring system according to an exemplary embodiment of the application. As shown in fig. 1, the implementation environment includes a vehicle 110 and a crash event monitoring system 120, where the crash event monitoring system 120 may be embedded in the vehicle 110 to implement monitoring of crash events of a vehicle-to-machine system in the vehicle 110, and the crash event monitoring system 120 includes, but is not limited to, a vehicle-mounted computer to implement efficient determination when the vehicle-to-machine system has a crash event, and efficient positioning of a crash type of the vehicle-to-machine system, so that a worker can timely and intuitively know occurrence of the crash event, thereby further promoting efficient and accurate repair of the crash event.
Referring to fig. 2, fig. 2 is a flowchart illustrating a crash event monitoring method according to an exemplary embodiment of the application. The method may be applied to the implementation environment shown in fig. 1, and it should be understood that the method may also be applied to other exemplary implementation environments, and the implementation environment to which the method is applied is not limited by the embodiment.
As shown in fig. 2, in an exemplary embodiment, the crash event monitoring method at least includes steps S210 to S240, which are described in detail below:
step S210, acquiring a screen capture picture of a display interface in the target system.
The target system can be a vehicle-to-machine system and other running systems comprising a display interface; the screen capturing picture is obtained by screen capturing a display interface of the target system in the operation process of the target system.
In an embodiment, before acquiring the screen capture picture of the display interface in the target system, the method further comprises: configuring a display function of a collapse display interface, wherein the display function comprises an interface style and collapse information; if an operation instruction for starting the display function is received, the display function is in a starting state so as to monitor the running state of the target system.
In this embodiment, the crash display interface refers to an interface presented by the display interface of the target system when a crash event occurs in the target system. In order to realize the display of the breakdown display interface, the display function of the breakdown display interface needs to be pre-configured, and then the display function is started before the operation of the target system, so that the breakdown display interface can be triggered and displayed when the operation state of the target system is monitored to be the breakdown state, and the automatic monitoring of the breakdown event is realized.
Referring to fig. 3, fig. 3 is a schematic diagram of a display function opening and closing interface according to an exemplary embodiment of the present application. As shown in FIG. 3, a display function of a Crash display interface is configured in the target system, such as a "Crash prompt" in the figure, when the function is turned on, crash monitoring is turned on, and when the vehicle system and any programs therein Crash, the Crash display interface is displayed.
It should be noted that, the display function of the configuration crash display interface needs to be configured in the engineering mode application, where the engineering mode is tool software used by an engineer to debug each configuration in the vehicle, and the configuration of the function is completed by entering in a password mode.
In a possible embodiment, in the engineering mode application, a crash monitoring system attribute is added to the target system, and the value is set to true or false, if the target system uses an Android (Android) system, a monitor for monitoring the change of the crash monitoring system attribute is registered in an AMS (ACTIVITY MANAGER SERVICE, active management service), and a crash interface display function is turned on/off according to the monitored attribute flag being true/false.
In an embodiment, before acquiring the screen capture picture of the display interface in the target system, the method further comprises: monitoring the operation information of a target system, and judging the operation state of the system and the operation state of a program according to the operation information; if the running state of the system is a breakdown state, determining that the breakdown type is a system breakdown; if the program running state is a crashed state, determining that the crashed type is program crashed; generating crash information according to the system operation information or the program operation information; generating a display instruction of the interface style according to the collapse type and the collapse information; switching the working thread into the main thread, and responding to the display instruction, and controlling the display interface to pop up the collapse display interface.
In this embodiment, when the target system is running, the running information of the target system can be monitored in real time, where the running information includes system running information of the target system and program running information of a program in the target system, and according to the running information corresponding to each of the target system and the program, the system running state and the program running state of the target system can be judged, where the running state includes a normal state and a crash state, and the crash type of the target system includes a system crash and a program crash, when the target system is in a system crash, the crash information is generated according to the system running information, and when the target system is in a program crash, the crash information is generated according to the program running information, so that the crash information corresponding to a crash event can be ensured to be obtained, and the reliability of the crash information is ensured.
After the breakdown type and the breakdown information are obtained, a display instruction is generated according to the breakdown type and the breakdown information, namely the display instruction carries a breakdown type field and a breakdown information field, the target system rapidly responds to the display instruction, the breakdown type and the breakdown information are analyzed, a breakdown display interface is popped up, at the moment, the interface style of the breakdown display interface is the interface style corresponding to the breakdown type, and the breakdown information is also displayed on the breakdown display interface, so that when a breakdown event occurs in the target system, the display interface of the target system pops up the breakdown display interface, the breakdown event of the target system can be known timely, the breakdown type can be known rapidly based on the specific interface style of the breakdown display interface, and rapid repair of the breakdown event can be realized based on the breakdown information.
It should be noted that, considering that the thread of the target system is the main thread, the display interface can pop up the crash display interface, so before the crash display interface is popped up, the working thread needs to be switched to the main thread, and thus, the normal pop-up of the crash display interface can be ensured.
In one possible embodiment, a PC (Personal Computer) computer is used to start a Monkey test tool (Monkey) in the target system through an ADB (android debug bridge), and randomly simulate the user operating the target system to trigger a crash event in the target system.
In this embodiment, the target system is on the production line, so that the test of the target system before use can be realized, and the performance of the target system can be tested and crashed repaired in advance, so that the event of crashing frequently occurs in the use process can be avoided, the user experience can be improved, and for example, the driving safety is effectively improved for the vehicle-mounted system.
In an embodiment, the display instruction carries a display duration, and the screenshot is intercepted based on a preset time interval, wherein the display duration is longer than the time interval.
In this embodiment, after the crash display interface pops up, the display duration disappears, so that after a crash event occurs in a certain program, even if the crash event cannot be recovered in time, the application of the target system about other programs is not affected.
Step S220, judging whether the screen capturing picture contains a preset interface style.
The type of the interface style is any one of a color style, a pattern style and a text style, and different sub-styles are set based on the collapse type of the target system.
In the embodiment of the application, the color pattern means that the screen capturing picture is a certain color, the color is displayed on the upper layer of the whole interface and is semitransparent, for example, when the color is red, the display effect is red semitransparent, so that the display of other contents of the display interface, such as the running of other programs, is not influenced; the pattern style refers to that a certain pattern exists in the screen capturing picture, the pattern can be displayed in a preset area of the interface or on the upper layer of the whole interface, and when the pattern style is the upper layer of the whole interface, the display effect is also required to be semitransparent color of a certain color; the text style refers to that a certain text or sentence exists in the screen capturing picture, the text or sentence can be displayed in a preset area of the interface or on the upper layer of the whole interface, and the display effect of the text or sentence is semitransparent color with a certain color when the text or sentence is displayed on the upper layer of the whole interface.
In addition, different crash types of the target system correspond to different sub-patterns, so that whether the system crashes or the program crashes can be intuitively known based on the specific sub-patterns in the screen capturing picture, and in general, the emergency degree of the system crashes is higher than that of the program crashes, and therefore, the development or working personnel can be warned differently due to the fact that the different sub-patterns are presented.
Specifically, the setting of the interface style includes: if the interface style is a color style, setting the interface style as a first color sub-style when the breakdown type is system breakdown, and setting the interface style as a second color sub-style when the breakdown type is program breakdown; if the interface style is pattern style, setting the interface style as a first pattern sub-style when the breakdown type is system breakdown, and setting the interface style as a second pattern sub-style when the breakdown type is program breakdown; if the interface style is a text style, setting the interface style as a first text sub-style when the breakdown type is system breakdown, and setting the interface style as a second text sub-style when the breakdown type is program breakdown.
Wherein the first color sub-pattern is for example translucent red, and the second color sub-pattern is for example translucent blue; a first pattern sub-pattern, such as a triangle pattern, and a second pattern sub-pattern, such as a circle pattern; the first sub-text style is a system crash, and the second sub-text style is a program crash.
Taking the color pattern as an example, please refer to fig. 4, fig. 4 is a schematic diagram of a crash display interface according to an exemplary embodiment of the present application, and as shown in fig. 4, the entire interface is translucent red.
In an embodiment, determining whether the screenshot includes a preset interface style includes: performing color matching, pattern matching and text matching on the screen capturing picture corresponding to a preset color pattern, a preset pattern and a preset text pattern respectively to obtain a matching result; if the matching result is that the screen capturing picture is not matched with the preset color pattern, the preset pattern and the preset text pattern, judging that the screen capturing picture does not contain the interface pattern; if the matching result is that the screen capturing picture is matched with any one of the preset color pattern, the preset pattern and the preset text pattern, judging that the screen capturing picture comprises the interface pattern.
In this embodiment, the colors need to be the same for color matching, the patterns need to be the same for pattern matching, and the words need to be the same for word matching.
Specifically, the matching of the color patterns includes: calibrating a first target pixel point in the screen capturing picture according to the preset pixel point position, wherein the first target pixel point is at least one; acquiring a first pixel value of a first target pixel point, and comparing the first pixel value with a preset pixel range once; if the first pixel value is in the pixel range, matching the screen capturing picture with a preset color pattern; if the first pixel value is not in the pixel range, the screen capturing picture is not matched with the preset color pattern.
As a possible embodiment, the color pattern matching mode is pixel value matching, when the pixel value of the screen capturing picture meets the pixel range requirement, the screen capturing picture is judged to comprise the preset color pattern, and therefore the reliability of the color matching is ensured.
In addition, considering that the color of the interface at the lower layer of the color pattern in the screen capture picture can influence the pixel value of the first target pixel point, the standard pixel of the preset color pattern is a pixel range, and only the pixel value of the first target pixel point is within the range, so that the erroneous judgment of the collapse display interface can be effectively avoided.
Taking the red, RGB (Red, green, blue, red, green, blue) color space as an example, the translucent red pixels are GRBs (246, 167, 167), and if the error is ±5, the pixel range is GRBs (246±5, 167±5).
In addition, in consideration of reliability of the determination result, the preset pixel point position is a point less affected by the lower layer interface color, and in consideration of determination efficiency, the preset pixel point position is a representative point.
Referring to fig. 5, fig. 5 is a schematic diagram of a calibration target pixel point according to an exemplary embodiment of the application. As shown in fig. 5, taking semitransparent red as an example, preferably, preset pixel positions are pixel positions on the upper edge and the right edge of the screen capturing interface, and considering the number of pixel positions, four positions, namely, the center position of the upper edge, the center position of the right edge and the center position of the right lower edge, are selected, and respectively correspond to the target pixel positions 1,2, 3, 4 and 5 in fig. 5, and are not easy to overlap with other interface information, so that the accuracy and the judgment rate of the judgment result are ensured.
In one possible embodiment, the matching time may be set, for example, to 50 milliseconds for one screen shot. In this way, the judgment efficiency can be further ensured.
In one possible embodiment, the screen capture is preprocessed before being color matched, wherein the preprocessing includes, but is not limited to, noise removal and color space conversion, a filter (such as mean filtering, gaussian filtering, etc.) is used to remove noise in the screen capture, so that the reliability of color matching is improved, and the screen capture is converted from RGB color space to HSV (Hue, saturation, value, hue, saturation, brightness) color space or Lab (Lab color space) to facilitate color matching.
Further, after if the first pixel value is within the pixel range, the method further includes: calibrating neighborhood pixel points of the first target pixel points to obtain a plurality of second target pixel points; obtaining a second pixel value of each second target pixel point, and carrying out secondary comparison on each second pixel value and a pixel range; if each second pixel value is in the pixel range, matching the screen capturing picture with a preset color pattern; if any second pixel value is not in the pixel range, the screen capturing picture is not matched with the preset color pattern.
In this embodiment, after the first target pixel points all meet the preset pixel range, the domain pixel point of each first target pixel point is taken as a second target pixel point, and when the pixel value of the second target pixel point meets the pixel range requirement, the screen capturing picture is judged to be matched with the preset color pattern, so that the reliability of the judging result is enhanced.
It should be noted that, the neighborhood pixel includes 4 fields, D fields, and 8 fields, and in this embodiment, the field pixel is one of the 4 fields, D fields, and 8 fields.
Referring to fig. 6, fig. 6 is a schematic diagram of a domain pixel according to an exemplary embodiment of the present application. Taking 8 fields as an example, taking a first target pixel point as a center, and taking 8 surrounding pixel points as second target pixel points, wherein the pixel values of the 8 pixel points are in line with a pixel range, namely, RGB values of each pixel point are compared, and the conditions that |G-246|is less than or equal to 5&|G-167| is less than or equal to 5 +|B-167| are satisfied.
Step S230, if the screen capture picture contains the interface style, determining that the screen capture picture is a collapse display interface, and determining that a target system has a collapse event.
Wherein, the crash display interface displays crash information.
The display of the collapse information is shown in fig. 3, wherein the collapse information is preferably displayed in the left part of the whole interface, so that the influence on the pixel values of the first target pixel point and the second target pixel point is avoided, and in addition, the display color of the collapse information has obvious difference from the color in the color pattern, such as green and semitransparent red.
In the embodiment of the application, if the screen capturing picture contains the interface style, the screen capturing picture can be rapidly judged to be a breakdown display interface, so that the breakdown event of the target system can be rapidly determined. In addition, if the screen capture picture is a collapse display interface, the screen capture picture is reserved so as to carry out collapse repair according to the collapse information on the screen capture picture, and if the screen capture picture is not the collapse display interface, the screen capture picture is discarded and is not saved.
In one embodiment, after determining that the target system has a crash event, the method comprises: determining a target collapse type according to the interface style; when the target breakdown type is system breakdown, analyzing breakdown information according to a system breakdown repairing program to generate a first breakdown repairing scheme, wherein the breakdown information at least comprises a system memory state, running process information and driver information; when the target crash type is program crash, analyzing crash information according to a program crash repairing program to generate a second crash repairing scheme, wherein the crash information at least comprises a package name, a process name, running time and an error call stack of the crash program.
The system crash repairing program refers to a set of various methods for repairing the system crash; program crash repair programs refer to a collection of methods of program crash repair. When a system crash or a program crash occurs, analyzing a crash reason according to the corresponding crash information, and determining at least one of the method sets as a target method, thereby generating a crash repair scheme.
In the embodiment, the crash repair is performed based on the interface style of the screen capturing picture and the crash information, so that the crash repair efficiency is improved.
Referring to fig. 7, fig. 7 is a flow chart illustrating another crash event monitoring method according to an exemplary embodiment of the application. As shown in FIG. 7, a PC computer executes a script to control a crash event monitoring system, a Monkey tool in a target system is started to simulate and operate the target system, a crash event is triggered in the target system, before the Monkey tool is started, a display function of a crash display interface of the target system is started, when the display function is started and the crash event occurs, crash information is acquired, a target system thread is switched from a working thread to a main thread, then the target system is controlled to pop up the crash display interface with the crash information, after the display duration is reached, the target system exits the crash display interface, in the operation process of the target system, the display interface of the target system is intercepted according to a time interval to obtain an interface pattern, then whether a screen capture picture comprises a preset interface pattern is judged, if not, the screen capture picture is discarded, if not, the crash event is determined to occur, the screen capture picture is reserved, and a crash repairing scheme is determined according to the screen capture picture.
According to the method for monitoring the breakdown event, firstly, the screen capturing picture of the display interface in the target system is obtained, then whether the screen capturing picture contains a preset interface pattern or not is judged, wherein the type of the interface pattern is any one of a color pattern, a pattern and a text pattern, different sub-patterns are set based on the breakdown type of the target system, finally, if the screen capturing picture contains the interface pattern, the screen capturing picture is determined to be the breakdown display interface, and the breakdown event of the target system is determined, wherein the breakdown display interface displays breakdown information. In this way, when a breakdown event occurs in the target system, firstly, according to the interface style contained in the screen capturing picture, the automatic monitoring of the breakdown event and the efficient judgment of the breakdown event occurring in the target system are realized, so that a worker can timely and intuitively know the occurrence of the breakdown event; secondly, based on different sub-patterns in the screen capturing picture, the high-efficiency positioning of the breakdown type of the target system is realized; third, based on the crash display interface, reliable crash types and crash information corresponding to the crash types are provided, and efficient and accurate repair of crash events can be further promoted.
Referring to FIG. 8, FIG. 8 is a block diagram of a crash event monitoring system according to an exemplary embodiment of the application. The system may be applied to the implementation environment shown in fig. 1, and it should be understood that the system may be applied to other exemplary implementation environments, and the application is not limited to the implementation environment of the system. As shown in fig. 8, in an exemplary embodiment, the crash event monitoring system 800 at least includes an acquisition module 810, a determination module 820, and a determination module 830, which are described in detail below:
an obtaining module 810, configured to obtain a screenshot of a display interface in a target system;
A judging module 820, configured to judge whether the screenshot picture includes a preset interface style, where the type of the interface style is any one of a color style, a pattern style and a text style, and set different sub-styles based on a breakdown type of the target system;
The determining module 830 is configured to determine that the screenshot is a crashed display interface if the screenshot includes an interface style, and determine that a target system has a crashed event, where the crashed display interface displays crashed information.
It should be noted that, the crash event monitoring system provided by the foregoing embodiment and the crash event monitoring method provided by the foregoing embodiment belong to the same concept, and the content of performing the operation by each module has been described in detail in the method embodiment, which is not described herein again.
The application also provides a vehicle which uses the crash event monitoring method or comprises the crash event monitoring system.
It should be noted that, the crash event monitoring method and the crash event monitoring system have been described in detail in the above method embodiments, and are not described herein again.
The application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to perform a crash event monitoring method as described above. The computer-readable storage medium may be contained in the vehicle described in the above embodiment or may exist alone without being assembled into the vehicle.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), a flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with a computer-readable computer program embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
The above embodiments are merely illustrative of the principles of the present application and its effectiveness, and are not intended to limit the application. Modifications and variations may be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the application. It is therefore intended that all equivalent modifications and changes made by those skilled in the art without departing from the spirit and technical spirit of the present application shall be covered by the appended claims.

Claims (11)

CN202410379688.2A2024-03-292024-03-29Crash event monitoring method, system, vehicle and storage mediumActiveCN118193321B (en)

Priority Applications (1)

Application NumberPriority DateFiling DateTitle
CN202410379688.2ACN118193321B (en)2024-03-292024-03-29Crash event monitoring method, system, vehicle and storage medium

Applications Claiming Priority (1)

Application NumberPriority DateFiling DateTitle
CN202410379688.2ACN118193321B (en)2024-03-292024-03-29Crash event monitoring method, system, vehicle and storage medium

Publications (2)

Publication NumberPublication Date
CN118193321A CN118193321A (en)2024-06-14
CN118193321Btrue CN118193321B (en)2024-10-11

Family

ID=91408674

Family Applications (1)

Application NumberTitlePriority DateFiling Date
CN202410379688.2AActiveCN118193321B (en)2024-03-292024-03-29Crash event monitoring method, system, vehicle and storage medium

Country Status (1)

CountryLink
CN (1)CN118193321B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN109117358A (en)*2017-06-232019-01-01百度在线网络技术(北京)有限公司test method and test device for electronic equipment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
KR100610487B1 (en)*2005-02-152006-08-08주식회사 팬택 Apparatus and method for screen composition when an event occurs in a mobile communication terminal
CN107480026A (en)*2017-06-222017-12-15深圳天珑无线科技有限公司Endpoint crashes processing method, terminal and the device with store function
CN107247637A (en)*2017-07-272017-10-13广州云测信息技术有限公司A kind of APP fault determination methods and device
CN115016973B (en)*2022-06-292025-07-15广州文远知行科技有限公司 A method, device, equipment and medium for reproducing program crash events

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN109117358A (en)*2017-06-232019-01-01百度在线网络技术(北京)有限公司test method and test device for electronic equipment

Also Published As

Publication numberPublication date
CN118193321A (en)2024-06-14

Similar Documents

PublicationPublication DateTitle
US10127689B2 (en)Mobile user interface design testing tool
US8059788B2 (en)Telephone software testing system and method
US8087005B2 (en)Software testing by groups
KR20080068385A (en) Computer-readable recording media having software test systems, methods and programs for executing the methods
CN110930131A (en)Vehicle maintenance method, device, equipment and medium
CN111915601B (en)Abnormality test method, device and system for intelligent terminal
CN110276201A (en)A kind of safety detection method of onboard system, system and service equipment
CN117593973A (en)Display fault detection method, device, equipment and storage medium
KR101460860B1 (en)GUI Test apparatus using test scenario model based on states and the method thereof
JP4098448B2 (en) Program verification method and apparatus
CN118193321B (en)Crash event monitoring method, system, vehicle and storage medium
US11241962B2 (en)Evaluation apparatus for display arbitration control and generation apparatus for rule definition file
CN115204539A (en)Host security baseline management method, device, equipment and medium
CN115599645A (en)Method and device for testing stability of linux drive module
CN109002694B (en) A method and device for locating problem points after application code obfuscation
CN116719736A (en)Test case generation method and device for testing software interface
CN116501625A (en)Application interface testing method and device, testing terminal, server and storage medium
CN112115057B (en)Automatic test method, device and equipment for application program page building flow
CN115856482A (en)MP 5-based 360-panorama abnormal working condition automatic testing method
JP2000322283A (en) Computer failure detection method
CN115033473A (en) Testing method and device based on software downtime location
CN109255233B (en)Vulnerability detection method and device
CN113395234A (en)Traffic hijacking monitoring method and device for promotion information
CN118152277B (en)Bootloader writing method, bootloader writing device, bootloader writing equipment and Bootloader writing medium
US20220027262A1 (en)Information processing system with intelligent program smoke testing

Legal Events

DateCodeTitleDescription
PB01Publication
PB01Publication
SE01Entry into force of request for substantive examination
SE01Entry into force of request for substantive examination
GR01Patent grant
GR01Patent grant

[8]ページ先頭

©2009-2025 Movatter.jp