The next section is some general information regarding to the state of the machine when the error happened: Error occurred at _000136. It is perfectly possible that the error was not caused in the executable file, but in a DLL that you loaded. In this case, the module is 8.exe, which is the same executable file. Then you see the module that caused the error, and the program location. If you're not doing anything like this, then it is likely that this is an error in the player itself. In this case, in Windows, error 0xc0000005 may be related to closing handles that are currently in use, that is, you're using a handle in one thread and you're closing it in another at the same time. Regardless of the error code, it might be useful to search online for it, and that way you can at least know whether or not the error is related to your program or not. In here, you can see that the error is an access violation, which corresponds to code 0xc0000005.
In this case, the error is: test 8.exe caused an Access Violation (0xc0000005) Then you get the error type and location. In general, always try to make sure you're using the last version of Unity to make your games. This is relatively important, as an error may be linked to a precise version of the player that you're using. The first line is the Unity Player version. It is difficult to understand what the problem is with a large game with such an error log, but there are some clues you may use to help yourself. There are many type of error logs, and this one is quite low level.
However, I would like to explain what are you looking at, and what to look for in an error log like the one you received, in case you get a similar error in the future.
0 kommentar(er)
