Search Unity

Bug [Burst] Could not find `burst.initialize`

Discussion in 'Burst' started by iamarugin, Nov 30, 2020.

  1. iamarugin

    iamarugin

    Joined:
    Dec 17, 2014
    Posts:
    883
    Unity 2020.1.12
    Burst 1.4.1

    Sometimes I get the following error in the console during play mode:

    Code (CSharp):
    1. Unexpected exception System.InvalidOperationException: Could not find `burst.initialize` function in library '7FFCF38A0000' ---> System.InvalidOperationException: Unable to load function entry `burst.initialize`
    2.   at Burst.Backend.UnmanagedLibrary+WindowsUnmanagedLibrary.GetFunctionByName (System.IntPtr libraryHandle, System.String functionName) [0x00025] in <004b2bef11fb4c94aedd2162289437e6>:0
    3.   at Burst.Backend.UnmanagedLibrary.GetFunctionByName (System.IntPtr libraryHandle, System.String functionName) [0x00000] in <004b2bef11fb4c94aedd2162289437e6>:0
    4.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager.CallBurstInitializeFunction (System.IntPtr libraryPtr, Burst.Compiler.IL.Jit.GetExternalFunctionPointerDelegate getExternalFunctionPointer) [0x00062] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    5.    --- End of inner exception stack trace ---
    6.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager.CallBurstInitializeFunction (System.IntPtr libraryPtr, Burst.Compiler.IL.Jit.GetExternalFunctionPointerDelegate getExternalFunctionPointer) [0x000c5] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    7.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager+<>c__DisplayClass7_2.<TryGetOrLoadLibrary>b__1 () [0x00000] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    8.   at Burst.Compiler.IL.Jit.JitCacheMethodValue.GetCachedPtrForAssemblies (System.Boolean ensureBurstInitializeHasBeenCalled, System.IntPtr& cachedPtr) [0x0004c] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    9.   at Burst.Compiler.IL.Jit.JitCompiler.CompileMethods (Mono.Cecil.MethodReference[] methodReferences, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x0027a] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    10.   at Burst.Compiler.IL.Jit.JitCompiler.CompileMethod (Mono.Cecil.MethodReference methodReference, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x0001c] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    11.   at Burst.Compiler.IL.Jit.JitCompilerService+CompilerThreadContext.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job) [0x00468] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    12.  
    13. While compiling job: System.Void Unity.Jobs.IJobExtensions/JobStruct`1<Space.BodyRaycastSystem/Space.<>c__DisplayClass_OnUpdate_LambdaJob1>::Execute(T&,System.IntPtr,System.IntPtr,Unity.Jobs.LowLevel.Unsafe.JobRanges&,System.Int32)
    14. at <empty>:line 0
    15.  
    After that if I try to close unity it get stuck.
    It looks like it appears pretty random, but I think it always related to recompilation of Burst code.
     
  2. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    not related to 2020.1 as this also happens in 19.4 with burst 1.4.1 and entities 0.11 as well.

    i'm assuming it's a burst issue.

    Burst 1.4.2 just came out today, hoping it fixes it (haven't tested yet)
     
  3. sheredom

    sheredom

    Unity Technologies

    Joined:
    Jul 15, 2019
    Posts:
    300
    We'd need a repro if we have any hope of solving this. As @tertle says, trying Burst 1.4.2 as a first step is a good shout!
     
  4. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    We updated to 1.4.2 today and it seems to have solved it. Should be able to confirm tomorrow.
     
    Last edited: Dec 1, 2020
    sheredom likes this.
  5. iamarugin

    iamarugin

    Joined:
    Dec 17, 2014
    Posts:
    883
    Oops, this post should be in DOTS forum, not in 2020.2 beta. Sorry about that.
     
  6. iamarugin

    iamarugin

    Joined:
    Dec 17, 2014
    Posts:
    883
    Issue still persist in 1.4.2
    If I will find stable reproducable, I will open the case and let you know.
     
    sheredom likes this.
  7. iamarugin

    iamarugin

    Joined:
    Dec 17, 2014
    Posts:
    883
    upload_2020-12-2_18-18-4.png
    A little more info: this happens immediately after that exception
    After reopening Unity everything works as expected
     
  8. reshen817

    reshen817

    Joined:
    Sep 9, 2012
    Posts:
    1
    As a temporary workaround, restarting Unity fixes it.

    In Unity 2020.1.15f1 Personal.

    Here's a stack trace for when it occurs on my machine:

    Code (CSharp):
    1. Unexpected exception System.InvalidOperationException: Could not find `burst.initialize` function in library '7FF9CB120000' ---> System.InvalidOperationException: Unable to load function entry `burst.initialize`
    2.   at Burst.Backend.UnmanagedLibrary+WindowsUnmanagedLibrary.GetFunctionByName (System.IntPtr libraryHandle, System.String functionName) [0x00025] in <004b2bef11fb4c94aedd2162289437e6>:0
    3.   at Burst.Backend.UnmanagedLibrary.GetFunctionByName (System.IntPtr libraryHandle, System.String functionName) [0x00000] in <004b2bef11fb4c94aedd2162289437e6>:0
    4.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager.CallBurstInitializeFunction (System.IntPtr libraryPtr, Burst.Compiler.IL.Jit.GetExternalFunctionPointerDelegate getExternalFunctionPointer) [0x00062] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    5.    --- End of inner exception stack trace ---
    6.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager.CallBurstInitializeFunction (System.IntPtr libraryPtr, Burst.Compiler.IL.Jit.GetExternalFunctionPointerDelegate getExternalFunctionPointer) [0x000c5] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    7.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager+<>c__DisplayClass7_2.<TryGetOrLoadLibrary>b__1 () [0x00000] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    8.   at Burst.Compiler.IL.Jit.JitCacheMethodValue.GetCachedPtrForAssemblies (System.Boolean ensureBurstInitializeHasBeenCalled, System.IntPtr& cachedPtr) [0x0004c] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    9.   at Burst.Compiler.IL.Jit.JitCompiler.CompileMethods (Mono.Cecil.MethodReference[] methodReferences, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x0027a] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    10.   at Burst.Compiler.IL.Jit.JitCompiler.CompileMethod (Mono.Cecil.MethodReference methodReference, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x0001c] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    11.   at Burst.Compiler.IL.Jit.JitCompilerService+CompilerThreadContext.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job) [0x00468] in <991cfc0e5dc843b2a9bb6d6c2e81a171>:0
    12.  
    13. While compiling job: System.Void Unity.Entities.JobChunkExtensions/JobChunkProducer`1<DOTS.Systems.FuelUsageSystem/DOTS.Systems.<>c__DisplayClass_OnUpdate_LambdaJob0>::Execute(Unity.Entities.JobChunkExtensions/JobChunkWrapper`1<T>&,System.IntPtr,System.IntPtr,Unity.Jobs.LowLevel.Unsafe.JobRanges&,System.Int32)
    14. at <empty>:line 0
    15.  
     
    LevonVH and BigRookGames like this.
  9. kadd11

    kadd11

    Joined:
    Mar 11, 2018
    Posts:
    33
    Still seeing this in 2020.3.6 with burst version 1.5.1

    Hard to give a concrete repro scenario, as it is sporadic. In my experience, it requires a killing the editor as shortly after seeing the error the editor hangs.
     
  10. iamarugin

    iamarugin

    Joined:
    Dec 17, 2014
    Posts:
    883
    Yea, same here with 1.5.4 and Unity 2020.3.10. It is however pretty rare.
     
  11. Per-Morten

    Per-Morten

    Joined:
    Aug 23, 2019
    Posts:
    119
    Happens here as well with 1.5.2 (on 2019.4.20, as well as 2020.3.11). Relatively rare here as well.
     
  12. sheredom

    sheredom

    Unity Technologies

    Joined:
    Jul 15, 2019
    Posts:
    300
    I haven't seen this since the 1.3 days locally - if any of you manage to get this in a semi-decent reproable state then we'd happily look at a repro!
     
  13. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    I still get this ~3-5 times a day on our large project (1500+ burst jobs) with burst 1.5.4, which is a lot less than previously but still common.

    I'll see if I can get a reasonably reliable repo other than just my normal workflow.

    -edit-

    i should also say i do see it but only rarely on my personal small libraries
     
    Last edited: Jun 23, 2021
  14. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    sheredom likes this.
  15. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    Maybe related but unity editor sometimes locks up at 99% on burst with lld.exe (which I assume is the LLVM linker) running at 100% on 1 core but never finishing. I can leave this an hour and it won't change.

    upload_2021-6-24_11-33-41.png
    Unfortunately a window was in front of the background tasks but I've seen this before and that end bracket pretty much confirms it (Not Responding)
     
    Last edited: Jun 24, 2021
  16. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    upload_2021-6-24_13-36-24.png
    Better screenshot

    This time I have 2x lld.exe running

    upload_2021-6-24_13-36-42.png

    Also I got 512+ of this error when entering play mode the previous time but the game seemed to run fine.

    Code (CSharp):
    1. Unexpected exception System.InvalidOperationException: Unable to find nested type `<>c__DisplayClass_OnUpdate_LambdaJob0` from typename `Beyond.MatchTargetTransformSystem+<>c__DisplayClass_OnUpdate_LambdaJob0` assembly `BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null`
    2.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.SimpleTypeReferenceString simpleTypeReferenceString) [0x000d9] in <f95137a4a8d747bbac814ce8830deb34>:0
    3.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.SimpleTypeReferenceString simpleTypeReferenceString) [0x0013f] in <f95137a4a8d747bbac814ce8830deb34>:0
    4.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.MethodReferenceString methodReferenceString) [0x0000e] in <f95137a4a8d747bbac814ce8830deb34>:0
    5.   at Burst.Compiler.IL.Jit.JitCompilerService+CompilerThreadContext.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job) [0x002af] in <f95137a4a8d747bbac814ce8830deb34>:0
    6.  
    7. While compiling job: Unity.Entities.JobChunkExtensions+JobChunkProducer`1[[Beyond.MatchTargetTransformSystem+<>c__DisplayClass_OnUpdate_LambdaJob0, BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]], Unity.Entities, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null::Execute(Unity.Entities.JobChunkExtensions+JobChunkWrapper`1[[Beyond.MatchTargetTransformSystem+<>c__DisplayClass_OnUpdate_LambdaJob0, BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]]&, Unity.Entities, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|Unity.Jobs.LowLevel.Unsafe.JobRanges&, UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null|System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
    8. at <empty>:line 0
    9.  
    10. Unexpected exception System.InvalidOperationException: Unable to find nested type `<>c__DisplayClass_OnUpdate_LambdaJob1` from typename `Beyond.MatchTargetTransformSystem+<>c__DisplayClass_OnUpdate_LambdaJob1` assembly `BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null`
    11.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.SimpleTypeReferenceString simpleTypeReferenceString) [0x000d9] in <f95137a4a8d747bbac814ce8830deb34>:0
    12.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.SimpleTypeReferenceString simpleTypeReferenceString) [0x0013f] in <f95137a4a8d747bbac814ce8830deb34>:0
    13.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.MethodReferenceString methodReferenceString) [0x0000e] in <f95137a4a8d747bbac814ce8830deb34>:0
    14.   at Burst.Compiler.IL.Jit.JitCompilerService+CompilerThreadContext.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job) [0x002af] in <f95137a4a8d747bbac814ce8830deb34>:0
    15.  
    16. While compiling job: Unity.Entities.JobChunkExtensions+JobChunkProducer`1[[Beyond.MatchTargetTransformSystem+<>c__DisplayClass_OnUpdate_LambdaJob1, BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]], Unity.Entities, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null::Execute(Unity.Entities.JobChunkExtensions+JobChunkWrapper`1[[Beyond.MatchTargetTransformSystem+<>c__DisplayClass_OnUpdate_LambdaJob1, BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]]&, Unity.Entities, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|Unity.Jobs.LowLevel.Unsafe.JobRanges&, UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null|System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
    17. at <empty>:line 0
    18.  
    19. Unexpected exception System.InvalidOperationException: Unable to find nested type `<>c__DisplayClass_CollectConsumables_LambdaJob0` from typename `Beyond.ConsumeHealthItemSystem+<>c__DisplayClass_CollectConsumables_LambdaJob0` assembly `BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null`
    20.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.SimpleTypeReferenceString simpleTypeReferenceString) [0x000d9] in <f95137a4a8d747bbac814ce8830deb34>:0
    21.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.SimpleTypeReferenceString simpleTypeReferenceString) [0x0013f] in <f95137a4a8d747bbac814ce8830deb34>:0
    22.   at zzzUnity.Burst.CodeGen.AssemblyLoader.Resolve (Burst.Compiler.IL.Helpers.MethodReferenceString methodReferenceString) [0x0000e] in <f95137a4a8d747bbac814ce8830deb34>:0
    23.   at Burst.Compiler.IL.Jit.JitCompilerService+CompilerThreadContext.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job) [0x002af] in <f95137a4a8d747bbac814ce8830deb34>:0
    24.  
    25. While compiling job: Unity.Entities.JobChunkExtensions+JobChunkProducer`1[[Beyond.ConsumeHealthItemSystem+<>c__DisplayClass_CollectConsumables_LambdaJob0, BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]], Unity.Entities, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null::Execute(Unity.Entities.JobChunkExtensions+JobChunkWrapper`1[[Beyond.ConsumeHealthItemSystem+<>c__DisplayClass_CollectConsumables_LambdaJob0, BeyondScience, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]]&, Unity.Entities, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|Unity.Jobs.LowLevel.Unsafe.JobRanges&, UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null|System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
    26. at <empty>:line 0
    Exiting play mode then recompiling caused Unity to lock up in the above state.

    Last thing in the Editor.log before the lockup is

    Code (CSharp):
    1. Reloading assemblies after finishing script compilation.
    2. Begin MonoManager ReloadAssembly
    3. Symbol file LoadedFromMemory is not a mono symbol file
    4. Symbol file LoadedFromMemory is not a mono symbol file
    5. Symbol file LoadedFromMemory is not a mono symbol file
    6. Symbol file LoadedFromMemory is not a mono symbol file
    7. Symbol file LoadedFromMemory is not a mono symbol file
    8. Symbol file LoadedFromMemory is not a mono symbol file
    9. Symbol file LoadedFromMemory is not a mono symbol file
    10. Symbol file LoadedFromMemory is not a mono symbol file
    11. Symbol file LoadedFromMemory is not a mono symbol file
    12. Symbol file LoadedFromMemory is not a mono symbol file
    13. Symbol file LoadedFromMemory is not a mono symbol file
    14. Symbol file LoadedFromMemory is not a mono symbol file
    15. Symbol file LoadedFromMemory is not a mono symbol file
    16. Symbol file LoadedFromMemory is not a mono symbol file
    17. Symbol file LoadedFromMemory is not a mono symbol file
    18. Symbol file LoadedFromMemory is not a mono symbol file
    19. Symbol file LoadedFromMemory is not a mono symbol file
    20. Native extension for WindowsStandalone target not found
    21. Refreshing native plugins compatible for Editor in 4.73 ms, found 28 plugins.
    22. Preloading 2 native plugins for Editor in 0.65 ms.
    -edit-
    if i kill both lld.exe from task manager Unity editor unfreezes then seems to work fine

    -edit2-

    i'm actually in a state now every recompile locks up on lld.exe until i kill it but i have no idea how to tell what burst job it is

    next time entering play mode i got this (the original error)

    Code (CSharp):
    1. Unexpected exception System.InvalidOperationException: Could not find `burst.initialize` function in library '7FFC4DC20000' ---> System.InvalidOperationException: Unable to load function entry `burst.initialize`
    2.   at Burst.Backend.UnmanagedLibrary+WindowsUnmanagedLibrary.GetFunctionByName (System.IntPtr libraryHandle, System.String functionName) [0x00025] in <b2dc5b19d1394c95a1a861711473d7d9>:0
    3.   at Burst.Backend.UnmanagedLibrary.GetFunctionByName (System.IntPtr libraryHandle, System.String functionName) [0x00000] in <b2dc5b19d1394c95a1a861711473d7d9>:0
    4.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager.CallBurstInitializeFunction (System.IntPtr libraryPtr, Burst.Compiler.IL.Jit.GetExternalFunctionPointerDelegate getExternalFunctionPointer) [0x00062] in <f95137a4a8d747bbac814ce8830deb34>:0
    5.    --- End of inner exception stack trace ---
    6.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager.CallBurstInitializeFunction (System.IntPtr libraryPtr, Burst.Compiler.IL.Jit.GetExternalFunctionPointerDelegate getExternalFunctionPointer) [0x000c5] in <f95137a4a8d747bbac814ce8830deb34>:0
    7.   at Burst.Compiler.IL.Jit.JitCacheLibraryManager+<>c__DisplayClass7_2.<TryGetOrLoadLibrary>b__1 () [0x00000] in <f95137a4a8d747bbac814ce8830deb34>:0
    8.   at Burst.Compiler.IL.Jit.JitCacheMethodValue.GetCachedPtrForHash (Burst.Compiler.IL.Helpers.Hash128 moduleHash, System.Boolean ensureBurstInitializeHasBeenCalled, System.IntPtr& cachedPtr, System.IntPtr& libraryPtr) [0x00040] in <f95137a4a8d747bbac814ce8830deb34>:0
    9.   at Burst.Compiler.IL.Jit.JitCompiler.CompileMethodInternal (Burst.Compiler.IL.Jit.JitResult result, System.Collections.Generic.List`1[T] methodsToCompile, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x001b5] in <f95137a4a8d747bbac814ce8830deb34>:0
    10.   at Burst.Compiler.IL.Jit.JitCompiler.CompileMethods (System.ValueTuple`2[Mono.Cecil.MethodReference,System.String][] methodReferences, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x002c1] in <f95137a4a8d747bbac814ce8830deb34>:0
    11.   at Burst.Compiler.IL.Jit.JitCompiler.CompileMethod (Mono.Cecil.MethodReference methodReference, System.String methodRefString, Burst.Compiler.IL.Jit.JitOptions jitOptions) [0x0002c] in <f95137a4a8d747bbac814ce8830deb34>:0
    12.   at Burst.Compiler.IL.Jit.JitCompilerService+CompilerThreadContext.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job) [0x00464] in <f95137a4a8d747bbac814ce8830deb34>:0
    13.  
    14. While compiling job: System.Void Unity.Entities.JobChunkExtensions/JobChunkProducer`1<Beyond.ServerSystems.ConsumeAbilityStart/Beyond.ServerSystems.<>c__DisplayClass_OnUpdate_LambdaJob0>::Execute(Unity.Entities.JobChunkExtensions/JobChunkWrapper`1<T>&,System.IntPtr,System.IntPtr,Unity.Jobs.LowLevel.Unsafe.JobRanges&,System.Int32)
    15. at <empty>:line 0
    16.  
    upload_2021-6-24_13-54-48.png
     

    Attached Files:

    Last edited: Jun 24, 2021
  17. sheredom

    sheredom

    Unity Technologies

    Joined:
    Jul 15, 2019
    Posts:
    300
    @tertle anyway we can get that project as a repro? We've never seen lld locking up, so we definitely want to investigate that!
     
  18. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    I can probably organize it in a few days. I just need to confirm with a few people and upload the ~50GB project.

    For the full day of work today I only had those 2 issues and I was somewhat trying to repo it so it's not super reliable but I'd say happens at least daily for me atm. It seems most common when switching branches with large code changes.

    The other problem you might have is, if I nuke my Library folder I sometimes stop having issues for a week before they return and not all our developers run into the issues as frequently. Anecdotally I'd say the better the machine, the more common these issues are.
     
    iamarugin and sheredom like this.
  19. tim_jones

    tim_jones

    Unity Technologies

    Joined:
    May 2, 2019
    Posts:
    287
    We've (finally!) found a repro for the "System.InvalidOperationException: Could not find `burst.initialize` function" error, and we'll fix it in a forthcoming version of Burst. Thanks everyone for your help in tracking this one down.
     
    kadd11, Yury-Habets and sheredom like this.
  20. iamarugin

    iamarugin

    Joined:
    Dec 17, 2014
    Posts:
    883
    Fantastic! Could you please tell, what went wrong when this error occurred?
     
  21. tertle

    tertle

    Joined:
    Jan 25, 2011
    Posts:
    3,759
    Did you still want that project or is all good now? was going to upload it today but saw the response.
     
    sheredom likes this.
  22. sheredom

    sheredom

    Unity Technologies

    Joined:
    Jul 15, 2019
    Posts:
    300
    @tertle thanks for the offer - but you can hold off for now. Once we get this out you can give it a whirl and tell us if it fixes it your end.

    @iamarugin basically there was a super subtle race condition to do with eager compilation, actual compilation (doing a CompileFunctionPointer), and cancelling compilation because the sources had changed. That's why we had never had a reliable repro before. But @tim_jones and the folk on this thread did some sort of mind-meld and worked it out.

    Thanks all!
     
    iamarugin likes this.