Information processing method and device, electronic equipment and readable storage medium
By distinguishing fatal and non-fatal exceptions in the scene editor, and executing the corresponding log logic output information without crashing, the scene editor stability problem is solved and the stability and efficiency of the development process is improved.
Patent Information
- Application Number
- CN202410028327.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-08
- Publication Date
- 2025-07-08
AI Technical Summary
The stability problems of the scene editor lead to frequent crashes, resulting in loss of art work and hindering the development process, especially in large-scale development teams.
Introduce an exception handling mechanism in the scene editor to distinguish between fatal and non-fatal exceptions, execute the first log logic and the second log logic respectively, and output runtime information or error information in the graphical user interface to keep the scene editor running and avoid crashes.
Reduces the number of crashes in the scene editor, improves stability, allows artists to continue working, and reduces interruptions in the development process.
Smart Images
Figure CN120268043A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technologies, and particularly to an information processing method, an information processing apparatus, an electronic device, and a computer-readable storage medium. Background Art
[0002] Scene resources in a program can be edited through a scene editor. Once the scene editor has a stability problem and crashes, the work done by artists up to the last save will be lost. If the probability of a crash occurring in a week is 5%, then for a development team of 10 people, the probability of a problem occurring once a week is: 1 - (1 - 0.05)^10 = 40.12%, and for a development team of 100 people, the probability of a problem occurring once a week is: 1 - (1 - 0.05)^100 = 99.41%.
[0003] As the scale of the development team expands and the development cycle lengthens, the man-day losses caused by the stability of the scene editor increase linearly. In large-scale development with more than a hundred people, crashes of the scene editor almost occur every week, and a large amount of art work will be lost. In addition, once the scene editor crashes, all artists need to wait for the problem to be fixed before they can continue to use the scene editor, which will cause the development process to be blocked and all artists cannot continue to work normally. Summary of the Invention
[0004] The present disclosure provides an information processing method, an information processing apparatus, an electronic device, and a computer-readable storage medium to solve or at least partially solve the above problems, as follows.
[0005] In a first aspect, the present disclosure provides an information processing method, the method including:
[0006] Determine an exception that occurs during the operation of the scene editor;
[0007] When the exception belongs to a first exception set, execute a first logging logic for the exception to output runtime information corresponding to the exception in the graphical user interface provided by the scene editor and enable the scene editor to continue running;
[0008] When the exception belongs to a second exception set, execute a second logging logic for the exception to output error information corresponding to the exception in the graphical user interface provided by the scene editor and enable the scene editor to continue running.
[0009] In a second aspect, the present disclosure further provides an information processing apparatus, the apparatus including:
[0010] Anomaly determination module, configured to determine anomalies that occur during the operation of the scenario editor;
[0011] The first anomaly handling module is configured to, when the anomaly belongs to the first anomaly set, execute the first logging logic for the anomaly to output the runtime information corresponding to the anomaly in the graphical user interface provided by the scenario editor, and cause the scenario editor to continue running;
[0012] The second anomaly handling module is configured to, when the anomaly belongs to the second anomaly set, execute the second logging logic for the anomaly to output the error message corresponding to the anomaly in the graphical user interface provided by the scenario editor, and cause the scenario editor to continue running.
[0013] In a third aspect, the present disclosure also provides an electronic device, including: a processor, a memory, and computer program instructions stored on the memory and executable on the processor;
[0014] When the processor executes the computer program instructions, the information method described in the first aspect above is implemented.
[0015] In a fourth aspect, the present disclosure also provides a computer-readable storage medium, in which computer program instructions are stored, and when the computer program instructions are executed by a processor, they are used to implement the information method described in the first aspect above.
[0016] The exemplary embodiments of the present disclosure have the following beneficial effects:
[0017] The information processing method provided by the present disclosure first determines anomalies that occur during the operation of the scenario editor; when the anomaly belongs to the first anomaly set, the first logging logic is executed for the anomaly to output the runtime information corresponding to the anomaly in the graphical user interface provided by the scenario editor, and cause the scenario editor to continue running; when the anomaly belongs to the second anomaly set, the second logging logic is executed for the anomaly to output the error message corresponding to the anomaly in the graphical user interface provided by the scenario editor, and cause the scenario editor to continue running, that is, an error reporting mechanism that does not cause the scenario editor to crash is adopted for anomalies belonging to the second anomaly set, rather than a processing mechanism such as an assertion mechanism that can cause the scenario editor to crash. In the present disclosure, for anomalies added to the first anomaly set and the second anomaly set, mechanisms for outputting the runtime information or error message corresponding to the anomaly can be executed respectively, without directly triggering the scenario editor to stop running. In this way, the number of crashes of the scenario editor can be reduced, and relevant personnel can perform anomaly handling by viewing the runtime information or error message. At this time, the art personnel can still use the scenario editor normally, and the stability of the scenario editor is improved, reducing the situation where the scenario development process is blocked. Description of the Drawings
[0018] Figure 1 is a flowchart of an information processing method provided by one embodiment of the present disclosure;
[0019] Figure 2 is a data schematic diagram of the reduction of man-day loss caused by the crash of a scenario editor provided by one embodiment of the present disclosure;
[0020] Figure 3 is a data schematic diagram of the reduction of the occurrence times of assertion logic in a scenario editor provided by one embodiment of the present disclosure;
[0021] Figure 4 is a block diagram of an information processing device provided by one embodiment of the present disclosure;
[0022] Figure 5 is a schematic logical structure diagram of an electronic device for implementing information processing provided by one embodiment of the present disclosure. Detailed Embodiments
[0023] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Apparently, the described embodiments are only some, but not all, of the embodiments of the present disclosure. Components of the embodiments of the present disclosure described and illustrated in the accompanying drawings herein can be arranged and designed in a variety of different configurations. Therefore, the detailed description of the embodiments of the present disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed present disclosure, but merely represents selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, every other embodiment obtained by those skilled in the art without creative efforts shall fall within the scope of protection of the present disclosure.
[0024] In this specification, the terms "a", "an", "the", and "said" are used to indicate the presence of one or more elements / components / etc.; the terms "comprising" and "having" are used to mean an open inclusion and mean that there may be additional elements / components / etc. in addition to the listed elements / components / etc.; the terms "first" and "second", etc. are only used as labels and are not a limitation on the quantity of their objects.
[0025] It should be understood that in the embodiments of the present disclosure, "at least one" means one or more, and "a plurality" means two or more. "And / or" is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. "Including A, B, and / or C" means including any one, any two, or all three of A, B, and C.
[0026] It should be understood that in the embodiments of the present disclosure, "B corresponding to A", "B corresponding to A relatively", "A corresponding to B relatively", or "B corresponding to A relatively" means that B is associated with A, and B can be determined according to A. Determining B according to A does not mean determining B only according to A. B can also be determined according to A and / or other information.
[0027] The present disclosure provides an information processing method. The execution subject of the information processing method provided by the present disclosure can be an electronic device or a server. The electronic device can be a desktop computer, a laptop computer, a game console, a smart watch, a tablet computer, a mobile phone, a television, etc., or other electronic devices, which are not specifically limited in this application. The server is used to provide background services for the client of the application program in the electronic device. For example, the server can be the background server of the above application program. The server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms, which are not specifically limited in this application.
[0028] Figure 1 The flowchart of an information processing method provided by one of the embodiments of the present disclosure is shown, as Figure 1 shown, and the method includes the following steps S101 to step S103.
[0029] Step S101: Determine the exceptions that occur during the operation of the scene editor.
[0030] Among them, the scene editor can be used to edit the virtual scene in the program. Exemplarily, such as the virtual scene in the game.
[0031] When an exception occurs during the operation of the scene editor, it can be determined whether the exception belongs to a preset first exception set or a preset second exception set.
[0032] Step S102: When the exception belongs to the first exception set, execute the first logging logic for the exception to output the runtime information corresponding to the exception in the graphical user interface provided by the scenario editor, and keep the scenario editor running.
[0033] Step S103: When the exception belongs to the second exception set, execute the second logging logic for the exception to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor, and keep the scenario editor running.
[0034] In the embodiments of the present disclosure, the following logical changes can be made to the scenario editor: The first exception set and the second exception set can be determined according to the exceptions that may occur during the operation of the scenario editor. Among them, the first exception set includes non-fatal exceptions that may occur during the operation of the scenario editor, and the second exception set includes fatal exceptions that may occur during the operation of the scenario editor.
[0035] In the embodiments of the present disclosure, configure the exception handling logic corresponding to the first exception set as the first logging logic (exemplarily, such as the logging logic at the log / info level), and configure the exception handling logic corresponding to the second exception set as the second logging logic (exemplarily, such as the logging logic at the error level). Among them, the first logging logic is a logging logic that does not affect compilation, and its main function is to output the runtime information corresponding to the exception. The second logging logic is a logging logic that affects compilation, and its main function is to output the error message corresponding to the exception.
[0036] Among them, both the first logging logic and the second logging logic are logging logics. Therefore, both the runtime information and the error message are the logging information corresponding to the exception. The logging information output by the first logging logic and the second logging logic can include the following contents: 1. The time of the error; 2. The line number of the corresponding code; 3. The user's error behavior; 4. The strategy for modifying the error behavior. Among them, the first three points are necessary, and the last one can be output if there is a corresponding strategy to modify the error behavior.
[0037] Based on the above-mentioned logical changes to the scenario editor, when the scenario editor is running, it is first possible to determine the exceptions that occur during the operation of the scenario editor. If the exception belongs to the exceptions in the first exception set, the first logging logic is executed, that is, the runtime information corresponding to the exception is output in the graphical user interface provided by the scenario editor, but the compilation is not affected, and the scenario editor continues to run. Therefore, when a specified non-fatal exception occurs during the operation of the scenario editor, the scenario editor will not crash. If the exception belongs to the exceptions in the second exception set, the second logging logic is executed, that is, the error message corresponding to the exception is output in the graphical user interface provided by the scenario editor, but the compilation cannot be performed unless the exception is fixed, and the scenario editor continues to run. Therefore, when a specified fatal exception occurs during the operation of the scenario editor, an error reporting mechanism can be used instead of the assertion (Assert) mechanism (a mechanism that can cause the scenario editor to crash when an exception occurs) used for fatal exceptions in the prior art. Therefore, the scenario editor will not crash either.
[0038] The information processing method provided by the present disclosure first determines the exceptions that occur during the operation of the scenario editor; when the exception belongs to the first exception set, the first logging logic is executed for the exception to output the runtime information corresponding to the exception in the graphical user interface provided by the scenario editor, and the scenario editor continues to run; when the exception belongs to the second exception set, the second logging logic is executed for the exception to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor, and the scenario editor continues to run, that is, an error reporting mechanism that does not cause the scenario editor to crash is used for the exceptions belonging to the second exception set, rather than a processing mechanism such as the assertion mechanism that can cause the scenario editor to crash. In the present disclosure, for the exceptions added to the first exception set and the second exception set, mechanisms for outputting the runtime information or error message corresponding to the exception can be executed respectively, without directly triggering the scenario editor to stop running. In this way, the number of crashes of the scenario editor can be reduced, and relevant personnel can handle the exceptions by viewing the runtime information or error message. At this time, the art personnel can still use the scenario editor normally, and the stability of the scenario editor is improved, reducing the situation where the scenario development process is blocked.
[0039] The non-fatal exceptions that may occur during the operation of the scenario editor can include the following two categories: non-fatal exceptions that may occur during the process of the scenario editor editing scenario resources in a program (such as a game program), and non-fatal exceptions that may occur during the process of the scenario editor running a program (such as a game program). Similarly, the fatal exceptions that may occur during the operation of the scenario editor can also include the following two categories: fatal exceptions that may occur during the process of the scenario editor editing scenario resources in a program (such as a game program), and fatal exceptions that may occur during the process of the scenario editor running a program (such as a game program).
[0040] Based on the two factors of fatality and the stage at which the exception occurs:
[0041] 1. Specifically, the first exception set (non-fatal exception set) can be divided into a third exception subset and a fourth exception subset. Among them, the third exception subset includes non-fatal exceptions that may occur during the process of the scenario editor editing scenario resources in a program, and the fourth exception subset includes non-fatal exceptions that may occur during the process of the scenario editor running a program;
[0042] 2. Specifically, the second exception set (fatal exception set) can be divided into a first exception subset and a second exception subset. Among them, the first exception subset includes fatal exceptions that may occur during the process of the scenario editor editing scenario resources in a program, and the second exception subset includes fatal exceptions that may occur during the process of the scenario editor running a program.
[0043] Exemplarily, taking game development as an example, the second exception subset may include one or more of the following exceptions: warehouse file corruption, world file corruption, skeleton file corruption, duplicate GUID, duplicate virtual path, missing scenario resources themselves, missing dependent resources of scenario resources, missing material textures, missing model resources on which the lod model depends, HDR texture not set to NoneCommpression, source file exists in the HDR texture directory, multiple files named source exist in the texture directory, inconsistent number of model layers and material layers, direction of Tracker particles is (0,0,0), number of material layers exceeds the specified value, and so on, but not limited to this.
[0044] Correspondingly, in an embodiment of the present disclosure, for exceptions belonging to the first exception subset in the second exception set, the log logic of the first log level can be executed, where the first log level indicates that if the exception is not processed, the program edited by the scenario editor cannot be compiled. For example, the first log level can be the error level in the log levels.
[0045] The first log level affects program compilation. Therefore, exceptions belonging to the first exception subset need to be fixed before program compilation to avoid unacceptable problems in the compiled program.
[0046] Correspondingly, in an embodiment of the present disclosure, the information processing method may further include the following steps: when the exception belongs to the second exception set, after outputting the error message corresponding to the exception in the graphical user interface provided by the scenario editor, in response to the compilation instruction for the program edited by the scenario editor, output a compilation error message in the graphical user interface provided by the scenario editor, where the compilation error message is used to indicate that the program edited by the scenario editor cannot be compiled.
[0047] After fixing the exception belonging to the second exception set, in response to the compilation instruction for the program edited by the scenario editor, compile the program edited by the scenario editor.
[0048] That is, for exceptions belonging to the second exception set, the program edited by the scenario editor cannot be compiled without fixing, and an error will be reported during compilation. It needs to be fixed before the program edited by the scenario editor can be compiled.
[0049] In an embodiment of the present disclosure, for fatal exceptions that may occur during the operation of the scenario editor, an exception reporting mechanism can be provided.
[0050] Correspondingly, the information processing method may further include the following steps S104 to step S105.
[0051] Step S104: When the scenario editor stops running due to an exception belonging to the second exception set, generate a reporting message for the exception belonging to the second exception set.
[0052] When the scenario editor stops running due to a fatal exception, a reporting message can be generated for the fatal exception.
[0053] Step S105: Upload the reporting message generated for the exception belonging to the second exception set to the server.
[0054] When the scenario editor crashes, the reporting message generated for the exception belonging to the second exception set can be uploaded to the server, where the server can be the server of the scenario editor or the server for parsing scenario editor exceptions, but is not limited thereto. The present disclosure does not aim to limit this.
[0055] The server can perform work such as parsing and fixing fatal exceptions based on the reporting message.
[0056] In an optional implementation manner, the above step S104 can be specifically implemented in the following way, including: generating a reporting message including a program database file (pdb file) and a memory dump file (dump file) for the exceptions belonging to the second exception set.
[0057] Among them, the dump file is a data file generated when the program crashes, which records the status information and execution stack information when the program crashes. By analyzing the dump file, the cause of the crash can be found, accelerating the troubleshooting of faults.
[0058] The pdb file (also known as a symbol file) maps the identifiers and statements in the project source code to the corresponding identifiers and descriptions in the compiled application. These mapping files link the debugger to the source code for debugging. When generating a project using standard debugging, the compiler creates the corresponding symbol file. With the pdb file, it is possible to know the line numbers and stack information of the program code corresponding to the binary package on the user side.
[0059] When debugging or statically analyzing a program, without the pdb file, one can only read the assembly code or rely on the ability of the disassembly tool to reverse-engineer the pseudo C code as much as possible. If there is a pdb file, then the disassembly tool or debugger can give more detailed information by parsing the pdb file, facilitating the correct parsing of the occurring crashes.
[0060] In an implementation manner of the present disclosure, for the exceptions belonging to the first exception subset and the second exception subset in the second exception set, in addition to the pdb file and the dump file, different reporting messages can also be provided.
[0061] Correspondingly, in an optional implementation manner, when the scenario editor stops running due to an exception belonging to the first exception subset in the second exception set, a reporting message including a pdb file, a dump file, an exception identifier, and exception information of a preset type can be generated for the exception belonging to the first exception subset in the second exception set. Among them, the exception identifier is used to indicate that an exception occurs during the process of the scenario editor editing the scenario resources in the program, that is, through this exception identifier, it can be indicated that the stage where the exception occurs is the resource editing stage, rather than the running stage of the edited program.
[0062] In an optional embodiment, the exception identifier can specifically be a placeholder.
[0063] Exemplarily, the exception information of the preset type can include the editing platform name, the engine version of the engine to which the scenario editor belongs, the script version, the resource version, the device ID where the scenario editor with the exception is located, the error type (including the log level, such as the error level), the device location information where the exception occurs (such as country, region, city, etc.), and is not limited thereto.
[0064] Further, in an optional specific embodiment, for an exception belonging to the third exception subset in the second exception set, the reported information may specifically be generated to include an exception identifier, target information, and exception information of a preset type. The target information includes one or more of the following: the version information of the scenario editor corresponding to the occurrence of an exception belonging to the first exception subset in the second exception set, the user information corresponding to the occurrence of an exception belonging to the first exception subset in the second exception set, and the device information corresponding to the occurrence of an exception belonging to the first exception subset in the second exception set.
[0065] Optionally, the user information may include one or more of the following: user ID, user email. It can be understood that the user information is not limited to the above examples.
[0066] Optionally, the device information may include one or more of the following: mac address, device ID. It can be understood that the device information is not limited to the above examples.
[0067] In another optional implementation manner, when the scenario editor stops running due to an exception belonging to the second exception subset in the second exception set, the reported information including a pdb file, a dump file, and exception information of a preset type is generated for the exception belonging to the second exception subset in the second exception set.
[0068] That is, when a fatal exception occurs when the scenario editor runs a program, only the regular exception information needs to be reported. When a fatal exception occurs when the scenario editor edits the scenario resources in the program, in addition to reporting the regular exception information, an exception identifier can also be reported to indicate that the current fatal exception is an exception that occurs in the scenario editor itself, rather than an exception that occurs in the program running in the scenario editor.
[0069] In addition, in an implementation manner of the present disclosure, the first exception subset may specifically include a scenario resource exception that may occur during the process of the scenario editor editing the scenario resources in the program, that is, the scenario resources in the program are in error.
[0070] In an optional embodiment, the scenario resource exception may include a missing exception of the scenario resource itself.
[0071] Correspondingly, the above step S103 may specifically include: when the exception is a missing exception of the first scenario resource itself, execute the second log logic for the missing exception of the first scenario resource itself to output the error message corresponding to the missing exception of the first scenario resource itself in the graphical user interface provided by the scenario editor, and make the scenario editor continue to run; display the scenario resources that are not missing in the scenario editor.
[0072] In an optional embodiment, the abnormal scene resources include the missing anomalies of the resources relied on by the scene resources;
[0073] Correspondingly, the above step S103 may specifically include: when the anomaly is the missing anomaly of the resources relied on by the first scene resource, execute the second log logic for the missing anomaly of the resources relied on by the first scene resource, so as to output the error message corresponding to the missing anomaly of the resources relied on by the first scene resource in the graphical user interface provided by the scene editor, and enable the scene editor to continue running; display the scene resources that are not missing in the scene editor, where the first scene resource that is not missing itself is displayed in a preset style in the scene editor.
[0074] In the prior art, if the scene resources in the program are missing, the scene editor will crash due to the execution of the Assert logic and cannot be entered. However, in the above embodiments of the present disclosure, if a certain scene resource is missing itself, the scene resource may not be displayed, and only the scene resources that are not missing need to be displayed, but the operation of the scene editor can still be maintained. Subsequently, the scene resource can be supplemented according to the log including the runtime information.
[0075] If the resources relied on by a certain scene resource are missing, the scene resource cannot be normally displayed, but the scene resource can be displayed in a preset style while maintaining the outline of the scene resource, for example, displayed in red, but the operation of the scene editor can still be maintained. Subsequently, the resources relied on by the scene resource can be supplemented according to the log including the error message.
[0076] Verified, as Figure 2 shown, the man-day loss caused by the crash of the scene editor has been significantly reduced, as Figure 3 shown, the occurrence times of the Assert logic in the scene editor have been significantly decreased.
[0077] Corresponding to the information processing method provided by the embodiments of the present disclosure, the embodiments of the present disclosure also provide an information processing device. As Figure 4 shown, the device 700 includes:
[0078] An anomaly determination module 701, configured to determine the anomalies that occur during the operation of the scene editor;
[0079] A first anomaly processing module 702, configured to execute the first log logic for the anomaly when the anomaly belongs to the first anomaly set, so as to output the runtime information corresponding to the anomaly in the graphical user interface provided by the scene editor, and enable the scene editor to continue running;
[0080] The second exception handling module 703 is used to execute the second log logic for the exception when the exception belongs to the second exception set, so as to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor, and enable the scenario editor to continue running.
[0081] Optionally, the device further includes:
[0082] A compilation error reporting module is used to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor when the exception belongs to the second exception set, and in response to a compilation instruction for the program edited by the scenario editor, output a compilation error message in the graphical user interface provided by the scenario editor.
[0083] Optionally, the device further includes:
[0084] A compilation module is used to compile the program edited by the scenario editor in response to a compilation instruction for the program edited by the scenario editor after the exception belonging to the second exception set is repaired.
[0085] Optionally, the device further includes:
[0086] A reporting information generation module is used to generate reporting information for the exception belonging to the second exception set when the scenario editor stops running due to a second exception belonging to the second exception set;
[0087] A reporting information uploading module is used to upload the reporting information generated for the exception belonging to the second exception set to the server.
[0088] Optionally, the reporting information generation module is specifically used for:
[0089] When the scenario editor stops running due to an exception belonging to the second exception set, generate reporting information including a program database file and a memory dump file for the exception belonging to the second exception set.
[0090] Optionally, the second exception set includes a first exception subset that may occur during the process of scenario resources in the program edited by the scenario editor;
[0091] The reporting information generation module includes:
[0092] The first reporting information generation sub-module is used to generate reporting information including a program database file, a memory dump file, an exception identifier, and exception information of a preset type for an exception belonging to the first exception subset in the second exception set when the scenario editor stops running due to the exception belonging to the first exception subset in the second exception set. Wherein, the exception identifier is used to indicate that an exception occurs during the process of the scenario editor editing scenario resources in a program.
[0093] Optionally, the first reporting information generation sub-module includes:
[0094] The reporting information generation unit is used to generate reporting information including a program database file, a memory dump file, an exception identifier, exception information of a preset type, and target information for an exception belonging to the first exception subset in the second exception set.
[0095] Wherein, the target information includes one or more of the following: the version information of the scenario editor corresponding to the occurrence of the exception belonging to the first exception subset in the second exception set, the user information corresponding to the occurrence of the exception belonging to the first exception subset in the second exception set, and the device information corresponding to the occurrence of the exception belonging to the first exception subset in the second exception set.
[0096] Optionally, the second exception set includes a second exception subset that can occur during the running program of the scenario editor.
[0097] The reporting information generation module includes:
[0098] The second reporting information generation sub-module is used to generate reporting information including a program database file, a memory dump file, and exception information of a preset type for an exception belonging to the second exception subset in the second exception set when the scenario editor stops running due to the exception belonging to the second exception subset in the second exception set.
[0099] Optionally, the second exception set includes a first exception subset that can occur during the process of the scenario editor editing scenario resources in a program, and the first exception subset includes scenario resource exceptions that can occur during the process of the scenario editor editing scenario resources in a program.
[0100] Optionally, the scenario resource exception includes a missing exception of the scenario resource itself.
[0101] The second exception handling module is specifically used for:
[0102] When the exception is a missing exception of the first scenario resource itself, execute the second log logic for the missing exception of the first scenario resource itself, so as to output the error message corresponding to the missing exception of the first scenario resource itself in the graphical user interface provided by the scenario editor, and make the scenario editor continue to run;
[0103] Display the scenario resources that are not missing in the scenario editor.
[0104] Optionally, the scenario resource exception includes a missing exception of a resource on which the scenario resource depends;
[0105] The second exception handling module is specifically used for:
[0106] When the exception is a missing exception of a resource on which the first scenario resource depends, execute the second log logic for the missing exception of the resource on which the first scenario resource depends, so as to output the error message corresponding to the missing exception of the resource on which the first scenario resource depends in the graphical user interface provided by the scenario editor, and make the scenario editor continue to run;
[0107] Display the scenario resources that are not missing in the scenario editor, where the first scenario resource that is not missing itself is displayed in a preset style in the scenario editor.
[0108] The information processing device provided by the present disclosure first determines an exception that occurs during the operation of the scenario editor; when the exception belongs to the first exception set, execute the first log logic for the exception, so as to output the runtime information corresponding to the exception in the graphical user interface provided by the scenario editor, and make the scenario editor continue to run; when the exception belongs to the second exception set, execute the second log logic for the exception, so as to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor, and make the scenario editor continue to run, that is, for an exception belonging to the second exception set, an error reporting mechanism that does not cause the scenario editor to crash is adopted, rather than a processing mechanism such as an assertion mechanism that can cause the scenario editor to crash. In the present disclosure, for exceptions added to the first exception set and the second exception set, mechanisms for outputting the runtime information or error message corresponding to the exception can be executed respectively, without directly triggering the scenario editor to stop running. In this way, the number of crashes of the scenario editor can be reduced, and relevant personnel can perform exception handling by viewing the runtime information or error message. At this time, the art personnel can still use the scenario editor normally, and the stability of the scenario editor is improved, reducing the situation where the scenario development process is blocked.
[0109] Next, an electronic device provided by an embodiment of the present disclosure will be introduced. Please refer to Figure 5 , Figure 5A schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. Among them, the information processing device described in the embodiment of the present disclosure can be deployed on the electronic device 800 to implement the functions in the embodiment of the present disclosure. Specifically, the electronic device 800 includes: a receiver 801, a transmitter 802, a processor 803, and a memory 804 (where the number of processors 803 in the electronic device 800 can be one or more, Figure 5 taking one processor as an example), where the processor 803 may include an application processor 8031 and a communication processor 8032. In some embodiments of the present disclosure, the receiver 801, the transmitter 802, the processor 803, and the memory 804 can be connected through a bus or other means.
[0110] The memory 804 may include a read-only memory and a random access memory, and provide instructions and data to the processor 803. A part of the memory 804 may also include a non-volatile random access memory (NVRAM). The memory 804 stores processor and operation instructions, executable modules, or data structures, or subsets thereof, or extended sets thereof, where the operation instructions may include various operation instructions for implementing various operations.
[0111] The processor 803 controls the operation of the execution device. In a specific application, the components of the execution device are coupled together through a bus system, where the bus system may include a power bus, a control bus, and a status signal bus in addition to a data bus. However, for the sake of clarity, all kinds of buses are called bus systems in the figure.
[0112] The method disclosed in the above embodiments of the present disclosure can be applied to or implemented by the processor 803. The processor 803 can be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above method can be completed by the integrated logic circuit in hardware or instructions in software form in the processor 803. The above-mentioned processor 803 can be a general-purpose processor, a digital signal processor (DSP), a microprocessor or a microcontroller, and can further include an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The processor 803 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present disclosure. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present disclosure can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by a combination of the hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory 804, and the processor 803 reads the information in the memory 804 and combines its hardware to complete the steps of the above method.
[0113] The receiver 801 can be used to receive input digital or character information, and generate signal inputs related to the relevant settings and function controls of the execution device. The transmitter 802 can be used to output digital or character information through the first interface; the transmitter 802 can also be used to send instructions to the disk group through the first interface to modify the data in the disk group; the transmitter 802 can also include a display device such as a display screen.
[0114] In the embodiments of the present disclosure, the application processor 8031 in the processor 803 is used to execute the information processing method in the embodiments of the present disclosure. It should be noted that the specific manner in which the application processor 8031 executes each step is based on the same concept as the various method embodiments in the present disclosure, and the technical effects brought by it are the same as those of the various method embodiments in the present disclosure. For specific content, reference can be made to the description in the method embodiments shown above in the present disclosure, and details will not be repeated here.
[0115] The embodiments of the present disclosure also provide a chip for running instructions, and this chip is used to execute the technical solution of the information processing method in the above embodiments.
[0116] An embodiment of the present disclosure also provides a computer-readable storage medium storing computer instructions, which, when run on a processor, cause the processor to execute the technical solution of the information processing method in the above embodiment.
[0117] An embodiment of the present disclosure also provides a computer program product including a computer program, which is used to execute the technical solution of the information processing method in the above embodiment when executed by a processor.
[0118] The above computer-readable storage medium may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, a magnetic disk, or an optical disk. The readable storage medium may be any available medium accessible by a general-purpose or special-purpose server.
[0119] It should be understood that the present disclosure is not limited to the exact structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.
[0120] Although the present disclosure is disclosed above in preferred embodiments, it is not intended to limit the present disclosure. Any person skilled in the art can make possible changes and modifications without departing from the spirit and scope of the present disclosure. Therefore, the protection scope of the present disclosure should be defined by the scope of the claims of the present disclosure.
Claims
1. An information processing method, characterized in that, The method includes: Determine the exceptions that occur during the operation of the scenario editor; When the exception belongs to the first exception set, execute the first logging logic for the exception to output the runtime information corresponding to the exception in the graphical user interface provided by the scenario editor, and enable the scenario editor to continue running; When the exception belongs to the second exception set, execute the second logging logic for the exception to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor, and enable the scenario editor to continue running.
2. The method according to claim 1, wherein The method further includes: When the exception belongs to the second exception set, after outputting the error message corresponding to the exception in the graphical user interface provided by the scenario editor, in response to the compilation instruction for the program edited by the scenario editor, output the compilation error message in the graphical user interface provided by the scenario editor.
3. The method according to claim 2, wherein The method further includes: After the exception belonging to the second exception set is repaired, in response to the compilation instruction for the program edited by the scenario editor, compile the program edited by the scenario editor.
4. The method according to claim 1, wherein The method further includes: When the scenario editor stops running due to an exception belonging to the second exception set, generate a reporting message for the exception belonging to the second exception set; Upload the reporting message generated for the exception belonging to the second exception set to the server.
5. The method according to claim 4, characterized in that The generating a reporting message for the exception belonging to the second exception set when the scenario editor stops running due to an exception belonging to the second exception set includes: When the scenario editor stops running due to an exception belonging to the second exception set, generate a reporting message including the program database file and the memory dump file for the exception belonging to the second exception set.
6. The method according to claim 5, wherein The second exception set includes a first exception subset that can occur during the process of scenario resources in the program edited by the scenario editor; The generating a reporting message including the program database file and the memory dump file for the exception belonging to the second exception set when the scenario editor stops running due to an exception belonging to the second exception set includes: When the scenario editor stops running due to an exception belonging to the first exception subset of the second exception set, generate a reporting message including the program database file, the memory dump file, the exception identifier, and the exception information of the preset type for the exception belonging to the first exception subset of the second exception set, where the exception identifier is used to indicate that an exception occurs during the process of scenario resources in the program edited by the scenario editor.
7. The method according to claim 6, characterized in that, The generating a reporting message including the program database file, the memory dump file, the exception identifier, and the exception information of the preset type for the exception belonging to the first exception subset of the second exception set includes: Generate a reporting message including the program database file, the memory dump file, the exception identifier, the exception information of the preset type, and the target information for the exception belonging to the first exception subset of the second exception set; Among them, the target information includes one or more of the following: the version information of the scenario editor corresponding to the occurrence of the exception belonging to the first exception subset in the second exception set, the user information corresponding to the occurrence of the exception belonging to the first exception subset in the second exception set, and the device information corresponding to the occurrence of the exception belonging to the first exception subset in the second exception set.
8. The method according to claim 5, characterized in that The second exception set includes a second exception subset that can occur during the running process of the scenario editor program; When the scenario editor stops running due to an exception belonging to the second exception set, generating a reporting information including a program database file and a memory dump file for the exception belonging to the second exception set, including: When the scenario editor stops running due to an exception belonging to the second exception subset in the second exception set, generating a reporting information including a program database file, a memory dump file, and exception information of a preset type for the exception belonging to the second exception subset in the second exception set.
9. The method according to claim 1, wherein The second exception set includes a first exception subset that can occur during the process of the scenario editor editing the scenario resources in the program, and the first exception subset includes scenario resource exceptions that can occur during the process of the scenario editor editing the scenario resources in the program.
10. The method according to claim 9, wherein The scenario resource exception includes a missing exception of the scenario resource itself; When the exception belongs to the second exception set, executing a second logging logic for the exception to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor and make the scenario editor continue to run, including: When the exception is a missing exception of the first scenario resource itself, executing the second logging logic for the missing exception of the first scenario resource itself to output the error message corresponding to the missing exception of the first scenario resource itself in the graphical user interface provided by the scenario editor and make the scenario editor continue to run; Displaying the scenario resources that are not missing in the scenario editor.
11. The method according to claim 9, wherein The scenario resource exception includes a missing exception of the resources on which the scenario resource depends; When the exception belongs to the second exception set, executing a second logging logic for the exception to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor and make the scenario editor continue to run, including: When the exception is a missing exception of the resources on which the first scenario resource depends, executing the second logging logic for the missing exception of the resources on which the first scenario resource depends to output the error message corresponding to the missing exception of the resources on which the first scenario resource depends in the graphical user interface provided by the scenario editor and make the scenario editor continue to run; Displaying the scenario resources that are not missing in the scenario editor, where the first scenario resource that is not missing itself is displayed in a preset style in the scenario editor.
12. An information processing apparatus, characterized in that, The device includes: An exception determination module, configured to determine an exception that occurs during the running process of the scenario editor; The first exception handling module is used to execute the first logging logic for the exception when the exception belongs to the first exception set, so as to output the runtime information corresponding to the exception in the graphical user interface provided by the scenario editor and enable the scenario editor to continue running; The second exception handling module is used to execute the second logging logic for the exception when the exception belongs to the second exception set, so as to output the error message corresponding to the exception in the graphical user interface provided by the scenario editor and enable the scenario editor to continue running.
13. An electronic device, characterized in that, including: a processor, a memory, and computer program instructions stored on the memory and executable on the processor; When the processor executes the computer program instructions, the information processing method according to any one of claims 1 to 11 above is implemented.
14. A computer-readable storage medium, characterized in that, Computer program instructions are stored in the computer-readable storage medium, and when the computer program instructions are executed by the processor, they are used to implement the information processing method according to any one of claims 1 to 11 above.