Search Issue Tracker
Fixed
Fixed in 1.6.1
Votes
0
Found in [Package]
1.6.0
Issue ID
BUR-1390
Regression
Yes
[Burst] Errors in console when opening project with special characters in it’s folder name
How to reproduce:
1. Open the users attached project
Expected result: No errors in console
Actual result: Console is filled with Burst errors
Reproducible with: 1.6.0-pre.2, 1.6.0 (2019.4.30f1, 2020.3.18f1, 2021.1.21f1, 2021.2.0b12, 2022.1.0a9)
Not reproducible with: 1.5.6 (2019.4.30f1, 2020.3.18f1, 2021.1.21f1)
Notes:
The errors go away after removing special characters for the project name
Special characters which cause the errors: ‘“;`|$%
Special characters which don’t cause the errors: <> \!_~\[]\{}@#^&*()+-=?.,-
Errors:
Time: -c: line 0: unexpected EOF while looking for matching `"'
Time: -c: line 1: syntax error: unexpected end of file
Unexpected exception Burst.Compiler.IL.Aot.AotLinkerException: The native link step failed. Check previous exception in the log - linker command line
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Joint Physics result in unexpected behaviors when used for articulated vehicles like buses or trucks
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts which worked with TMP Font Asset Creator
hessel_mm
May 24, 2022 08:32
This is still happening for me in Unity 2021.3.0f1, macOS 12.3.1 (21E258), I get this error 12 times after each recompile:
```
Unexpected exception Burst.Compiler.IL.Aot.AotLinkerException: The native link step failed. Check previous exception in the log - linker command line : "/Users/username/Development/Projects/project-name-here/Library/PackageCache/com.unity.burst@1.6.5/.Runtime/hostmac/lld -flavor darwin -arch x86_64 -macosx_version_min 10.8 -sdk_version 10.9 -r -dylib -o '/Users/username/Development/Projects/project-name-here/Temp/Burst/burst-aot9tlyk1sz.odm/2231d79f6014197043c74980a0f2f4f5.bundle' '/Users/username/Development/Projects/project-name-here/Library/PackageCache/com.unity.burst@1.6.5/.Runtime/libs/burstRTL_m64.a' '/Users/username/Development/Projects/project-name-here/Temp/Burst/burst-aot9tlyk1sz.odm/lib_burst_generated_part_.o' '/Users/username/Development/Projects/project-name-here/Temp/Burst/burst-aot9tlyk1sz.odm/lib_burst_generated_part__globals.o'"
at Burst.Compiler.IL.Aot.AotNativeLinkBase.RunNativeLinkerTool (System.String command, System.String arguments, System.String errorMessage, System.String commandType, System.String workingDirectory, System.Boolean muteOutputs) [0x000d0] in <44dde17bb74e4847ac96fa1d80d6d096>:0
at Burst.Compiler.IL.Aot.AotNativeLinkLLVMMacOS.Link (Burst.Backend.TargetCpu targetCpu, System.Collections.Generic.List`1[T] inputFiles, System.String outputFile, System.Boolean enableDebugInfo) [0x0013d] in <44dde17bb74e4847ac96fa1d80d6d096>:0
at Burst.Compiler.IL.Aot.AotCompiler.Link (System.Collections.Generic.List`1[T] groups, System.String nameSuffix, Burst.Compiler.IL.Aot.AotCompilerOptions compilerOptions, System.IO.TextWriter consoleOut, System.IO.TextWriter consoleError) [0x00234] in <44dde17bb74e4847ac96fa1d80d6d096>:0
at Burst.Compiler.IL.Jit.Providers.BaseOnDiskProvider.CommonDiskCompileModule (Burst.Compiler.IL.NativeCompiler+ModulePair module, Burst.Compiler.IL.NativeCompiler nativeCompiler, Burst.Compiler.IL.NativeCompilerOptions options, Burst.Compiler.IL.Jit.JitOptions jitOptions, Burst.Compiler.IL.Helpers.Hash128& moduleHash) [0x000c3] in <44dde17bb74e4847ac96fa1d80d6d096>:0
at Burst.Compiler.IL.Jit.Providers.OnDiskJitProvider.BeginCompileModule (Burst.Compiler.IL.NativeCompiler+ModulePair module, Burst.Compiler.IL.NativeCompiler nativeCompiler, Burst.Compiler.IL.NativeCompilerOptions options, Burst.Compiler.IL.Jit.JitOptions jitOptions, Burst.Compiler.IL.Helpers.Hash128& moduleHash, Burst.Compiler.IL.Jit.JitCacheManager jitCacheManager, Burst.Compiler.IL.Jit.GetExternalFunctionPointerDelegate getExternalFunctionPointer, System.Action& invokeBurstInitialize) [0x00000] in <44dde17bb74e4847ac96fa1d80d6d096>:0
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) [0x00678] in <44dde17bb74e4847ac96fa1d80d6d096>:0
at Burst.Compiler.IL.Jit.JitCompiler.CompileMethods (Burst.Compiler.IL.Jit.JitMethodGroupRequest& request, Burst.Compiler.IL.Jit.JitCompilationRequestType requestType) [0x00209] in <44dde17bb74e4847ac96fa1d80d6d096>:0
at Burst.Compiler.IL.Jit.JitCompiler.CompileMethod (Burst.Compiler.IL.Jit.MethodReferenceWithMethodRefString method, Burst.Compiler.IL.Jit.JitOptions jitOptions, Burst.Compiler.IL.Jit.JitCompilationRequestType requestType) [0x00023] in <44dde17bb74e4847ac96fa1d80d6d096>:0
at Burst.Compiler.IL.Jit.JitCompilerService+CompilerThreadContext.Compile (Burst.Compiler.IL.Jit.JitCompilerService+CompileJob job, Burst.Compiler.IL.Jit.JitCompilationRequestType requestType) [0x00491] in <44dde17bb74e4847ac96fa1d80d6d096>:0
While compiling job: System.Void UnityEngine.Jobs.IJobParallelForTransformExtensions/TransformParallelForLoopStruct`1<UnityEngine.Rendering.Universal.DecalUpdateCachedSystem/UpdateTransformsJob>::Execute(T&,System.IntPtr,System.IntPtr,Unity.Jobs.LowLevel.Unsafe.JobRanges&,System.Int32)
at <empty>:line 0
```
(I changed the user and project name to something else using the same range of characters)
When I copy the burst package to another folder and remove the `@1.6.5` part, the error disappears. But the package manager / cache adds the @ separator automatically, which doesn't make this a sustainable solution.
Some other colleagues with the same macOS and Unity versions don't seem to have the problem. we are unable to spot any differences in our configurations that would influence the handling of an @ character in a file path though...