Table of Contents

Crash Analysis on Windows

For crashes on native (Windows) and Unity Editor (Windows), refer to the following instructions.

Getting the crash location during development

The information required for debugging in Visual Studio is shown in the figure below.

crash Windows

The cause of the crash is

Exception thrown at 0x00007FFB7747317B (EasyAR.dll) in HelloAR.exe: 0xC0000005: Access violation writing location 0x0000000000009C40.

The call stack is

>	EasyAR.dll!00007ffb7747317b()	Unknown
    EasyAR.dll!00007ffb774719cc()	Unknown
    EasyAR.dll!00007ffb77477db3()	Unknown
    EasyAR.dll!00007ffb77474eb3()	Unknown
    ucrtbase.dll!00007ffbfee910b2()	Unknown
    kernel32.dll!00007ffc009f7c24()	Unknown
    ntdll.dll!00007ffc0148d721()	Unknown

The dynamic library loading address is

0x00007FFB75BC0000

When there is content related to EasyAR.dll in the call stack, it may indicate that the crash is related to EasyAR; if not, there is a high probability that the crash is not related to EasyAR.

Getting the crash location during development (Unity)

When developing applications with Unity, you can also use Unity logs to analyze crashes.

Unity logs are divided into Unity Editor logs and Unity Player logs, which can be obtained through the following methods.

Unity environment Operating system Log location
Editor Windows %LOCALAPPDATA%\Unity\Editor\Editor.log
Player Windows %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log

Editor logs can also be opened through the Open Editor Log command in the upper-right menu of the Console window.

Managed exceptions (C#) can be viewed in the Console window of the Unity Editor (Unity main menu Window -> General -> Console).

  • Version numbers of EasyAR Sense and EasyAR Sense Unity Plugin

    e.g., 4.7.0.11800-cf8e24e30

  • Community/Enterprise edition

  • Platform

    Win32

  • CPU architecture

    x86_64/x86