Burst 1.8.15 Constant Crash on Compile

Update to latest burst 1.8.15 and turning burst compilation on just crashes 100% while recompiling in my project

Repro rate 7/7 (100%) just going to Burst → Enable Compilation
Unity 6000.0.3f1
Deleting burst cache does not help
-edit- full Library deletion and reimport doesn’t help

Stacks from logs

and

IN-76518

1 Like

Thanks, will take a look.

Well it seems like Unity 6000.0.4 bumped min burst version to 1.8.15 so I’m now blocked from upgrading Unity (unless I throw a copy of burst 1.8.14 in the /Packages folder I guess)

I just encountered both errors last night (which I will refer to as Error1 and Error2 respectively) across two of my projects. However, my steps for triggering them and how I resolved them are a bit different. So I will document here what happened in case it sheds additional light on the problem to help track down this issue.

I started off in ProjectA, where at some point I disabled Burst compilation to iterate on some code a bit faster. After iterating for a while, I re-enabled Burst and encountered Error1. Notably, this was on Unity 6000.0.3f1 and Burst 1.8.13. I restarted the editor and encountered the same crash on startup. I reported this as IN-77476

While I was waiting for that bug to upload, I decided to try and upgrade Project B from 6000.0.2f1 to 6000.0.3f1. This was also using Burst 1.8.13. Doing so resulted in Error2 upon immediately opening up the project. Reported as IN-77478

Once ProjectA’s report was submitted, I wiped out the Library cache and temp folders completely and reopened the project, and I encountered Error2 this time. I did the same for Project B with the same result.

I then installed Unity 6000.0.4f1, and opened Project A in it, which inherently updated Burst to 1.8.15. This opened successfully, and I was able to test my iterations in Burst. I did the same for ProjectB.

So far, Unity 6000.0.3f1 seems to be the real culprit for me, but I might just need more time experimenting to encounter more issues.

I hope this info proves to be helpful! Best of luck tracking this one down!

Hi. Any new update?

Apologies, the issue turned out to be slightly trickier than we expected. We are preparing a 1.8.16 to correct the issues introduced in 1.8.15. If nothing else is encountered a new 1.8.16 should be available shortly, (end of week)

2 Likes

Hi, Burst 1.8.16, which contains the fix for this issue, has been released & is accessible through the Package Manager.

1 Like