Information reporting method, device, medium and electronic device

Abstract

The present disclosure relates to an information reporting method, device, medium and electronic device, the method comprising: obtaining a target cause that triggers an application crash, wherein the application is used to play multimedia data belonging to a preset scene and multimedia data that does not belong to the preset scene; obtaining crash data corresponding to the target cause, wherein each crash data corresponds to a multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene; determining the distribution of target crash data in all the crash data, wherein the target crash data includes crash data whose corresponding multimedia data belongs to the preset scene; and determining whether to report abnormal information based on a preset threshold and the distribution, which is conducive to improving the stability of the application when playing multimedia data belonging to the preset scene.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to an information reporting method, device, medium and electronic device. Background Art

[0002] Currently, many applications are installed on most clients, such as mobile clients. If an application crashes, such as a flashback, while the user is using the application, it will affect the user experience. Summary of the invention

[0003] This summary is provided to introduce concepts in a brief form that will be described in detail in the detailed description below. This summary is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0004] In a first aspect, the present disclosure provides an information reporting method, comprising:

[0005] Obtaining a target cause of an application crash, wherein the application is used to play multimedia data belonging to a preset scene and multimedia data not belonging to the preset scene;

[0006] Acquire crash data corresponding to the target cause, wherein each piece of crash data corresponds to a piece of multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene;

[0007] Determining distribution of target crash data in all the crash data, wherein the target crash data includes crash data whose corresponding multimedia data belongs to the preset scenario;

[0008] Determine whether to report abnormal information based on the preset threshold and the distribution situation.

[0009] In a second aspect, the present disclosure provides an information reporting device, comprising:

[0010] A first acquisition module, configured to acquire a target cause of an application crash, wherein the application is configured to play multimedia data belonging to a preset scene and multimedia data not belonging to the preset scene;

[0011] A second acquisition module is used to acquire crash data corresponding to the target cause, wherein each piece of crash data corresponds to a piece of multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene;

[0012] A first determining module, configured to determine a distribution of target crash data in all the crash data, wherein the target crash data includes crash data of which corresponding multimedia data belongs to the preset scenario;

[0013] The second determination module is used to determine whether to report abnormal information according to a preset threshold and the distribution situation.

[0014] In a third aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, which implements the steps of the method described in the first aspect when the program is executed by a processing device.

[0015] In a fourth aspect, the present disclosure provides an electronic device, including:

[0016] a storage device having a computer program stored thereon;

[0017] A processing device is used to execute the computer program in the storage device to implement the steps of the method in the first aspect.

[0018] Through the above technical scheme, for crash data corresponding to the target cause, the scene identification information used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene can be used to count the crash data of the corresponding multimedia data belonging to the preset scene, and then determine the distribution of the target crash data in all crash data, so as to determine whether to report abnormal information based on the preset threshold and distribution. In this way, it can avoid that the crash of the multimedia data of the preset scene is submerged, and the back-end personnel can optimize the application based on the abnormal information, which is conducive to improving the stability of the application when playing multimedia data belonging to the preset scene.

[0019] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale. In the drawings:

[0021] Figure 1 The figure is a flow chart of an information reporting method according to an exemplary embodiment.

[0022] Figure 2 The figure is a schematic diagram of a process of obtaining crash data according to an exemplary embodiment.

[0023] Figure 3 The invention is a block diagram of an information reporting device according to an exemplary embodiment.

[0024] Figure 4 The diagram is a schematic structural diagram of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION

[0025] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0026] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0027] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0028] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0029] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0030] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0031] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0032] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0033] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0034] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet the relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0035] At the same time, it is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0036] In the related technology, for example, taking an application for playing short videos as an example, the application can support the playback of promotional short videos and non-promotional short videos. Generally, the volume of promotional short videos is smaller than that of non-promotional short videos. Therefore, if promotional short videos and non-promotional short videos are not distinguished, all video data that cause application crashes are uniformly counted and compared with the set threshold. Even if there are more crashes caused by promotional short videos, the alarm will not be triggered because the set threshold is not reached, and the crashes caused by promotional short videos are easily submerged. Especially in the test environment, the number of users is small and the coverage of crashes is incomplete. However, after the application is launched, the number of users is large. If the crashes caused by promotional short videos are not repaired immediately, the user experience will be seriously affected.

[0037] Figure 1 FIG. 1 is a flow chart of an information reporting method according to an exemplary embodiment. Figure 1 As shown, the embodiment of the present disclosure provides an information reporting method, which can be executed by an electronic device, specifically, by an information reporting device, which can be implemented by software and / or hardware and configured in the electronic device. Figure 1 As shown, the method may include the following steps:

[0038] Step 110, obtaining a target cause of the application crash, wherein the application is used to play multimedia data belonging to a preset scene and multimedia data not belonging to the preset scene;

[0039] Step 120, acquiring crash data corresponding to the target cause, wherein each piece of crash data corresponds to a piece of multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to a preset scene;

[0040] Step 130, determining the distribution of target crash data in all crash data, wherein the target crash data includes crash data of which corresponding multimedia data belongs to a preset scenario;

[0041] Step 140: Determine whether to report abnormal information based on the preset threshold and distribution.

[0042] Among them, the target reason causing the application crash within a preset time period can be obtained, and the preset time period can be 3 hours, 5 hours, etc.

[0043] Among them, the target cause of the application crash in the preset period can be obtained. The preset period can be a period when the number of users using the application is greater than the preset number of users, and the period can be set based on experience. It is understandable that when the number of users is large, the application will crash more often, and it is more necessary to report abnormal information when the application is unstable, which is also more conducive to developers to find the location of the fault point, so that timely optimization can be carried out to ensure the stability of the application and improve the user experience.

[0044] The above steps 110 to 140 may be completed in a test environment.

[0045] Among them, a timed task can be set, and the timed task is used to regularly obtain the target cause of the application crash. In another embodiment, the timed task can be used to regularly obtain the target cause of the application crash within a preset time period. In another embodiment, the timed task can be used to regularly obtain the target cause of the application crash within a preset period of time.

[0046] Among them, the reasons for application crashes can be insufficient resources (memory and storage space), system errors, third-party library and plug-in problems, uncertain variables and memory leaks, etc.

[0047] Insufficient resources: When the resources required by an application exceed the available resources of the system, it is easy to cause the application to crash.

[0048] System error: The environment in which the application runs is the operating system. If an error occurs in the operating system, it can easily cause the application to crash.

[0049] Third-party library and plug-in issues: The application may rely on some third-party libraries or plug-ins. If there are problems with these libraries or plug-ins, it is easy to cause the application to crash.

[0050] Uncertain variables: Applications that use random numbers or variable components that are not well-defined during application execution can easily cause application crashes.

[0051] Memory leak: After applying for memory, the application is unable to release it or fails to release it in time, resulting in continuous consumption of system memory, and ultimately causing program crashes or performance degradation, which in turn causes application crashes.

[0052] The target cause may include the causes in the top N of the ranking results among all the causes that cause the application to crash within a preset time period, and the ranking result is obtained by ranking all the causes from high to low according to the number of crashes based on all the causes that cause the application to crash, and N is a positive integer greater than 0. Analyzing the target causes with a larger magnitude to realize information reporting can achieve the purpose of saving resources.

[0053] For example, the causes of application crashes may include insufficient resources, system errors, third-party library and plug-in problems, uncertain variables, and memory leaks. Within the preset time of hours, the number of crashes caused by insufficient resources, system errors, third-party library and plug-in problems, uncertain variables, and memory leaks are 1000, 1500, 2050, 1450, and 5000 times, respectively. All causes are sorted from high to low according to the number of crashes, and the causes in the sorting results are memory leaks, third-party library and plug-in problems, system errors, uncertain variables, and insufficient resources. If N is 3, the target causes are the top three memory leaks, third-party library and plug-in problems, and system errors in the sorting results.

[0054] The preset scene may be a promotion scene. In the promotion scene, multimedia data of the content to be promoted is played in the application. Taking an application that plays short videos as an example, the multimedia data belonging to the preset scene may be a short video covering the content to be promoted, and correspondingly, the multimedia data not belonging to the preset scene may be a short video not covering the content to be promoted.

[0055] The crash data corresponding to the target cause may refer to data causing the application to crash due to the target cause, and each piece of crash data corresponds to one piece of multimedia data.

[0056] Among them, the data platform that provides crash data can support the ability to add custom fields. Therefore, by adding a scene identification field and a value corresponding to the scene identification field, the value can be understood as scene identification information. For example, when playing multimedia data belonging to a preset scene, the value of the scene identification field corresponding to the multimedia data is set to true, and when playing multimedia data that does not belong to the preset scene, the value of the scene identification field corresponding to the multimedia data is set to false. During the use of the application, the multimedia data that causes the application to crash is captured, and the crash data corresponding to the multimedia data is constructed, and the crash data carries the value corresponding to the scene identification field. When the value is true, it indicates that the multimedia data belongs to the preset scene, that is, the application crashes under the preset scene. When the value is false, it indicates that the multimedia data does not belong to the preset scene, that is, the application crashes under a non-preset scene, thereby realizing the distinction between multimedia data of a preset scene and multimedia data of a non-preset scene that causes the application to crash. It can be understood that true and false can be understood as scene identification information.

[0057] Among them, the distribution situation can be used to characterize the proportion of the target crash data in all crash data. The above-mentioned step of determining whether to report abnormal information based on the preset threshold and the distribution situation may include the following steps: when the proportion is greater than or equal to the preset threshold, determine to report the abnormal information; when the proportion is less than the preset threshold, determine not to report the abnormal information.

[0058] Among them, when the proportion is greater than or equal to the preset threshold, the abnormal information can be reported according to the configured preset reporting method, and the preset reporting method includes real-time reporting or non-real-time reporting.

[0059] For example, non-real-time reporting may be performed at time intervals.

[0060] Through the above technical scheme, for crash data corresponding to the target cause, the scene identification information used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene can be used to count the crash data of the corresponding multimedia data belonging to the preset scene, and then determine the distribution of the target crash data in all crash data, so as to determine whether to report abnormal information based on the preset threshold and distribution. In this way, it can avoid that the crash of the multimedia data of the preset scene is submerged, and the back-end personnel can optimize the application based on the abnormal information, which is conducive to improving the stability of the application when playing multimedia data belonging to the preset scene.

[0061] In a possible manner, the above method further includes the following steps: receiving configuration data corresponding to the application, wherein the configuration data includes a preset threshold.

[0062] In this way, different preset thresholds can be configured for different applications, thereby achieving a reasonable configuration of the preset thresholds.

[0063] In a possible manner, the above N may be carried in configuration data, thereby achieving personalized configuration of N corresponding to different applications.

[0064] In a possible manner, the above-mentioned step of obtaining the crash data corresponding to the target cause can be implemented in the following manner: based on the target cause, constructing a data request, the data request is used to request the crash data corresponding to the target cause; sending the data request to the data platform through an application programming interface; receiving the crash data corresponding to the target cause successfully returned by the data platform in response to the data request through the application programming interface.

[0065] Figure 2 FIG. 1 is a flow chart showing a process of obtaining crash data according to an exemplary embodiment. Figure 2 The above-mentioned electronic device can be, for example, an alarm robot. The alarm robot periodically requests the data platform for the top n reasons with the largest crash magnitude within a preset time period, and the top n reasons are the target reasons; the data platform returns a reason list to the alarm robot, and the reason list includes the top n reasons; the alarm robot extracts each reason in the reason list and constructs a data request corresponding to each reason; the alarm robot requests the data platform to send a data request, and the data request is used to request issue details containing a scene identification field, where the issue details containing the scene identification field can be understood as the above-mentioned crash data; the data platform returns the issue details to the alarm robot; based on the issue details, the alarm robot determines whether the proportion of the value of the scene identification field that is true reaches a preset threshold, that is, determines whether the proportion of the target crash data in all crash data is greater than the preset threshold; when the alarm robot determines that the proportion of the value of the scene identification field that is true reaches the preset threshold, the alarm robot sends an alarm message to the development terminal, that is, reports the abnormal information to the development terminal.

[0066] In this way, the development terminal can receive the situation that causes the application to crash, which is convenient for the developers of the development terminal to optimize, reduce the probability of the application crashing in the preset scenario, and improve the stability of the application in playing multimedia data belonging to the preset scenario, thereby improving the user experience of the application.

[0067] In addition, it is worth mentioning that the communication between the alarm robot and the data platform can be carried out through the application programming interface.

[0068] Figure 3 is a block diagram of an information reporting device according to an exemplary embodiment. Figure 3 , the information reporting device 300 includes:

[0069] A first acquisition module 301 is used to acquire a target cause of an application crash, wherein the application is used to play multimedia data belonging to a preset scene and multimedia data not belonging to the preset scene;

[0070] A second acquisition module 302 is used to acquire crash data corresponding to the target cause, wherein each piece of crash data corresponds to a piece of multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene;

[0071] A first determining module 303 is used to determine the distribution of target crash data in all the crash data, wherein the target crash data includes crash data whose corresponding multimedia data belongs to the preset scenario;

[0072] The second determination module 304 is used to determine whether to report abnormal information according to a preset threshold and the distribution situation.

[0073] In a possible manner, the distribution condition is used to characterize the proportion of the target crash data in all the crash data, and the second determining module 304 includes:

[0074] A first determination submodule, configured to determine to report abnormal information when the proportion is greater than or equal to a preset threshold;

[0075] The second determining submodule is used to determine not to report the abnormal information when the proportion is less than the preset threshold.

[0076] In a possible manner, the second acquisition module 302 includes:

[0077] A construction submodule, configured to construct a data request based on the target cause, wherein the data request is used to request crash data corresponding to the target cause;

[0078] A sending submodule, used for sending the data request to the data platform through an application programming interface;

[0079] The receiving submodule is used to receive, through the application programming interface, crash data corresponding to the target cause that is successfully returned by the data platform in response to the data request.

[0080] In a possible manner, the first acquisition module 301 is specifically used to periodically acquire the target cause of the application crash.

[0081] In a possible manner, the target cause includes the causes whose sorting results are in the top N among all the causes that cause the application to crash within the preset time period. The sorting result is based on the number of crashes of all the causes that cause the application to crash, and all the causes are sorted from high to low according to the number of crashes, where N is a positive integer greater than 0.

[0082] In a possible manner, the information reporting device 300 further includes:

[0083] A receiving module is used to receive configuration data corresponding to the application, wherein the configuration data includes the preset threshold.

[0084] In a possible manner, the first determination submodule is specifically used to report abnormal information according to a configured preset reporting method when the proportion is greater than or equal to a preset threshold, and the preset reporting method includes real-time reporting or non-real-time reporting.

[0085] The implementation of each module in the device 300 may refer to the method embodiment, which will not be described in detail in this embodiment.

[0086] The embodiment of the present disclosure further provides a computer-readable medium on which a computer program is stored, and the program performs the steps of the above method when executed by a processing device.

[0087] The present disclosure also provides an electronic device, including:

[0088] a storage device having a computer program stored thereon;

[0089] A processing device is used to execute the computer program in the storage device to implement the steps of the above method.

[0090] Reference below Figure 4 , which shows a schematic diagram of the structure of an electronic device 400 suitable for implementing the embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 4 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0091] like Figure 4As shown, the electronic device 400 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage device 408 into a random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the electronic device 400 are also stored. The processing device 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0092] Typically, the following devices may be connected to the I / O interface 405: an input device 406 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 407 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 408 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 409. The communication device 409 may allow the electronic device 400 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 4 The electronic device 400 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0093] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 409, or installed from the storage device 408, or installed from the ROM 402. When the computer program is executed by the processing device 401, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0094] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0095] In some embodiments, the electronic device can communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0096] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0097] The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: obtains the target cause that causes the application to crash, wherein the application is used to play multimedia data belonging to a preset scene and multimedia data that does not belong to the preset scene; obtains crash data corresponding to the target cause, wherein each crash data corresponds to a multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene; determines the distribution of target crash data in all the crash data, wherein the target crash data includes crash data whose corresponding multimedia data belongs to the preset scene; determines whether to report abnormal information based on a preset threshold and the distribution.

[0098] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0099] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0100] The modules involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a module does not, in some cases, limit the module itself.

[0101] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0102] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0103] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

[0104] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0105] Although the subject matter has been described in language specific to structural features and / or method logic actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims. Regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Claims

1. An information reporting method, characterized in that: include: Obtaining a target cause of an application crash, wherein the application is used to play multimedia data belonging to a preset scene and multimedia data not belonging to the preset scene; Acquire crash data corresponding to the target cause, wherein each piece of crash data corresponds to a piece of multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene; Determining distribution of target crash data in all the crash data, wherein the target crash data includes crash data whose corresponding multimedia data belongs to the preset scenario; Determine whether to report abnormal information based on the preset threshold and the distribution situation.

2. The method according to claim 1, characterized in that The distribution condition is used to characterize the proportion of the target crash data in all the crash data, and determining whether to report abnormal information according to a preset threshold and the distribution condition includes: When the proportion is greater than or equal to a preset threshold, determining to report abnormal information; When the proportion is less than the preset threshold, it is determined not to report the abnormal information.

3. The method according to claim 1, characterized in that The acquiring the crash data corresponding to the target cause includes: Based on the target cause, constructing a data request, the data request being used to request crash data corresponding to the target cause; Sending the data request to the data platform through an application programming interface; The crash data corresponding to the target cause is received through the application programming interface and is successfully returned by the data platform in response to the data request.

4. The method according to claim 1, characterized in that: The target reason for obtaining the application crash includes: Get the target reason that caused the application crash regularly.

5. The method according to claim 1, characterized in that The target cause includes the causes that are ranked in the top N positions among all the causes that cause the application to crash within the preset time period. The ranking result is based on the number of crashes of all the causes that cause the application to crash, and all the causes are ranked from high to low according to the number of crashes. N is a positive integer greater than 0.

6. The method according to claim 1, characterized in that The method further comprises: Configuration data corresponding to the application is received, wherein the configuration data includes the preset threshold.

7. The method according to claim 2, characterized in that When the proportion is greater than or equal to a preset threshold, determining to report abnormal information includes: When the proportion is greater than or equal to a preset threshold, the abnormal information is reported according to a configured preset reporting method, where the preset reporting method includes real-time reporting or non-real-time reporting.

8. An information reporting device, characterized in that: include: A first acquisition module, configured to acquire a target cause of an application crash, wherein the application is configured to play multimedia data belonging to a preset scene and multimedia data not belonging to the preset scene; A second acquisition module is used to acquire crash data corresponding to the target cause, wherein each piece of crash data corresponds to a piece of multimedia data, and the crash data carries scene identification information, and the scene identification information is used to indicate whether the multimedia data corresponding to the crash data belongs to the preset scene; A first determining module, configured to determine a distribution of target crash data in all the crash data, wherein the target crash data includes crash data of which corresponding multimedia data belongs to the preset scenario; The second determination module is used to determine whether to report abnormal information according to a preset threshold and the distribution situation.

9. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processing device, the steps of the method described in any one of claims 1 to 7 are implemented.

10. An electronic device, characterized in that: include: a storage device having a computer program stored thereon; A processing device, configured to execute the computer program in the storage device to implement the steps of the method according to any one of claims 1 to 7.

Images