Search Issue Tracker

Fixed

Fixed in 1.8.13, 2.0.0-pre.12

Votes

11

Found in [Package]

1.8.11

2.0.0-pre.4

Issue ID

BUR-2599

Regression

Yes

Burst Complier throws the error "Internal compiler error for Burst ILPostProcessor on Assembly-CSharp-Editor. Exception: System.ArgumentNullException: Value cannot be null. (Parameter 'self')" when the Target Platform is set to Android

Package: Burst

-

Reproduction steps:
1. Open the attached project “ReproProject”
2. Ensure to switch to target Platform to Android
3. Observe the Console Window

Expected result: No errors in the console
Actual result: The error “zzzUnity.Burst.CodeGen.BurstILPostProcessor: ILPostProcessor has thrown an exception: System.InvalidOperationException: Internal compiler error for Burst ILPostProcessor on Assembly-CSharp-Editor. Exception: System.ArgumentNullException: Value cannot be null. (Parameter 'self')“ is thrown

Reproducible with: 1.8.8, 1.8.10, 1.8.11 (2023.1.0a19, 2023.2.5f1, 2023.3.0b2)
Not reproducible with: 1.8.8, 1.8.10, 1.8.11 (2021.3.34f1, 2022.3.17f1, 2023.1.0a18)

Reproducible on: macOS Intel 14.2.1
Not Reproducible on: No other environment was tested

Notes:
- The error ceases to occur when the “/r:System.Drawing.dll” is removed from the csc.rsp file.
- The regression happened in the Editor versions and not the Package itself
- The issue is not reproducible when the Build Target is on Standalone

Full Error:

Processing assembly Library/Bee/artifacts/1300b0aEDbg.dag/Unity.Collections.BurstCompatibilityGen.dll, with 125 defines and 254 references

processors: Unity.Jobs.CodeGen.JobsILPostProcessor, zzzUnity.Burst.CodeGen.BurstILPostProcessor
running Unity.Jobs.CodeGen.JobsILPostProcessor
running zzzUnity.Burst.CodeGen.BurstILPostProcessor
zzzUnity.Burst.CodeGen.BurstILPostProcessor: ILPostProcessor has thrown an exception: System.InvalidOperationException: Internal compiler error for Burst ILPostProcessor on Unity.Collections.BurstCompatibilityGen. Exception: System.ArgumentNullException: Value cannot be null. (Parameter 'self')
at Mono.Cecil.Rocks.TypeDefinitionRocks.GetConstructors(TypeDefinition self)
at zzzUnity.Burst.CodeGen.FunctionPointerInvokeTransform.Initialize(AssemblyResolver loader, AssemblyDefinition assemblyDefinition, TypeSystem typeSystem)
at zzzUnity.Burst.CodeGen.FunctionPointerInvokeTransform.Run(AssemblyDefinition assemblyDefinition)
at zzzUnity.Burst.CodeGen.BurstILPostProcessor.Process(ICompiledAssembly compiledAssembly)
at zzzUnity.Burst.CodeGen.BurstILPostProcessor.Process(ICompiledAssembly compiledAssembly)
at Unity.ILPP.Runner.PostProcessingPipeline.PostProcessAssemblyAsync(PostProcessAssemblyRequest request, Action`2 progressSink)
PostProcessing failed: System.InvalidOperationException: Internal compiler error for Burst ILPostProcessor on Unity.Collections.BurstCompatibilityGen. Exception: System.ArgumentNullException: Value cannot be null. (Parameter 'self')
at Mono.Cecil.Rocks.TypeDefinitionRocks.GetConstructors(TypeDefinition self)
at zzzUnity.Burst.CodeGen.FunctionPointerInvokeTransform.Initialize(AssemblyResolver loader, AssemblyDefinition assemblyDefinition, TypeSystem typeSystem)
at zzzUnity.Burst.CodeGen.FunctionPointerInvokeTransform.Run(AssemblyDefinition assemblyDefinition)
at zzzUnity.Burst.CodeGen.BurstILPostProcessor.Process(ICompiledAssembly compiledAssembly)
at zzzUnity.Burst.CodeGen.BurstILPostProcessor.Process(ICompiledAssembly compiledAssembly)
at Unity.ILPP.Runner.PostProcessingPipeline.PostProcessAssemblyAsync(PostProcessAssemblyRequest request, Action`2 progressSink)
at Unity.ILPP.Runner.PostProcessingService.PostProcessAssembly(PostProcessAssemblyRequest request, IServerStreamWriter`1 responseStream, ServerCallContext context)
Unhandled Exception: System.InvalidOperationException: Post processing failed

Comments (7)

  1. MKark

    Mar 27, 2024 10:03

    P.S: The current workaround is to delete the Library folder. After that the build succeeds.

  2. MKark

    Mar 27, 2024 09:48

    2023.1.17f1, Burst 1.8.9, Standalone Linux

    Same problem here. Windows version builds fine and opens in editor.
    The Linux build throws this error when trying to open the editor or running a build from the command line.

  3. ATMLVE

    Mar 02, 2024 05:17

    I get an error referencing similar files while trying to use fishnet. You can add some random method that does nothing and suddenly you start seeing these errors. Through voodoo magic you may get it to go away for a while, but it always returns eventually.

  4. TrueJollyRoger

    Feb 11, 2024 05:10

    Okay. I think I approximately found out what was an issue.
    The trick is to ignore going to "safe mode" and select "ignore", because otherwise you are to be locked out of BuildSetting/PlayerSetting and you literally can't do anything in "safe mode".

    Where you have to play with Scripting Backend which is highly likely switched from IL2CPP to mono after going up a version (I suspect other settings below may affect it too, so play with them).
    Once done Unity reassemble itself and bug will go.
    I tried with different copies of repo. It may not work from the first time, try switching it back to mono etc.
    It never took me more then two switches.
    Hope it will help.

  5. TrueJollyRoger

    Feb 11, 2024 04:02

    Can confirm it for Window build for Android. Happens after moving project from 2022 to 2023. Deleting Library folder doesn't help.
    It looks like it's unrelated to platform you build for, but to local install of Unity.
    My college doesn't have this error on the same branch.
    Bug is 100% roadblock to even use unity.
    Bug doesn't repro if you create new project in Unity.

  6. graham_unity923

    Feb 09, 2024 22:29

    I am a Dev at a AAA studio.. Once this bug is fixed we will be able to proceed with a pretty substantial WebGPU proof of concept web app.

  7. craftsmanbeck

    Feb 03, 2024 00:15

    Can confirm the same error being thrown on Windows, targeting WebGL, 2023.3.0b5, Burst 1.18.12. Issue prevents the project from being opened outside of safe mode, prevents entering playmode, etc. Issue also occured not just in Assembly-CSharp-Editor, but also Unity.Burst.Editor, Unity.Animation.Rigging.Editor, and Unity.RenderPipelines.Core.Editor. No csc.rsp file on my end.

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.