Table of Contents

Crash analysis on windows

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

Crash location acquisition during development

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

crash Windows

The crash reason is

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

The code 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 content related to EasyAR.dll exists in the code call stack, it may indicate the crash is related to EasyAR; if not, there is a high probability the crash is unrelated to EasyAR.

Crash location acquisition during development (unity)

When developing applications using Unity, Unity logs can also be used 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

The editor log can also be opened via the Open Editor Log command in the upper-right menu of the Console window.

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

  • EasyAR Sense and EasyAR Sense Unity Plugin version numbers

    e.g., 4.7.0.11800-cf8e24e30

  • Community edition/Enterprise edition

  • Platform

    Win32

  • CPU architecture

    x86_64/x86