Search Issue Tracker

Not Reproducible

Votes

0

Found in [Package]

1.8.18

Issue ID

BUR-2775

Regression

No

Crash on mono_domain_set during burst compilation when opening a specific project

Package: Burst

-

Reproduction steps:
1. Open the attached "ASDQWE" project
2. Observe the Editor

Expected result: The Editor opens successfully
Actual result: The Editor crashes

Reproducible with: 1.8.18 (6000.0.25f1, 6000.1.0a2)
Could not test with: 2021.3.45f1, 2022.3.52f1 (Multiple compilation errors)

Reproducible on: MacOS 14.6.1 Intel
Not reproducible on: No other environment tested

Workaround: Remove the Library folder

Notes:
- The rest of the crash stack trace lines are “(Unknown)"
- After removing the library, the issue does not occur again

First few lines of the stack trace:

{noformat}#0 0x000001915966af in mono_domain_set
#1 0x0000010adfd3b1 in BurstCompilerService::CompileAsync(ScriptingMethodPtr, void*, int, void (*)(void*, int, void*), void (*)(void*, BurstLogType, char const*, char const*, int), char const*)
#2 0x0000010ae028c3 in CompileAsyncDelegateMethod(ScriptingObjectPtr, char const*)
#3 0x0000010a9d4643 in BurstCompilerService_CUSTOM_CompileAsyncDelegateMethod(ScriptingBackendNativeObjectPtrOpaque*, BindingsManagedSpan*)
#4 0x00000195d50332 in (wrapper managed-to-native) Unity.Burst.LowLevel.BurstCompilerService:CompileAsyncDelegateMethod_Injected (object,UnityEngine.Bindings.ManagedSpanWrapper&) [{0x7ff6a42aa160} + 0xa2] (0x195d50290 0x195d50408) [0x18d482a80 - Unity Child Domain]
#5 0x00000195d4d64b in Unity.Burst.BurstCompiler:Compile (object,System.Reflection.MethodInfo,bool,bool) [{0x7ff6e97e0cd8} + 0xf8b] [./Library/PackageCache/com.unity.burst/Runtime/BurstCompiler.cs :: 414u] (0x195d4c6c0 0x195d4d922) [0x18d482a80 - Unity Child Domain]
#6 0x00000000000000 in (Unknown){noformat}

  1. Resolution Note:

    The crash is fixed in later releases of Unity. However, there a still errors logged which appear to be due to Burst somehow not being properly installed in the project. The .Runtime folder does not exist. Reinstalling the Burst package fixes that.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.