This has been happening to me for at least 3 months. It’s very annoying. I’m also using Odin, Burst, Ryzen 5950x
This just started happening to me today. I imported a beta package (A* pathfinding project) and it uses burst compiler. That seems to be the common thread among those having the issue.
! We are also using the !* pathfinding project!
2 Likes
@LeonhardP Any update on this? Looks like a lot of people are having this issue.
3 Likes
@LeonhardP Bumping this one, experiencing the same issue frequently once I started using Burst in my project.
1 Like
Also having this issue in latest 2021. It happens many times per day.
Any word on this?
** Edit: For anyone having this, a work around for me is to just save a script in Visual Studio, then close it and tab back into Unity. That seems to solve the issue without needing to restart the whole project.
For me, I haven’t had the problem for a long time (~a month) when disabling Burst. So it seems to be very much tied to the use of Burst. As others have suggested: turn off Burst compilation when you’re not using it.
It’s also happening for me around 8 times a day. It’s sadly very irritating ~~ (Unity 2021.2.5f1)
I created a new thread in Burst forum, let’s see if it helps.
1 Like
Same problem here, Unity 2021.2.5.
Regarding previous reports, I am using Rider IDE & the Burst package, no 3rd party assets.
At the moment only restart seems to fix it only for a little while. I haven’t figured out what exactly triggers it.
A fix as soon as possible would be greatly appreciated, this bug is a true workflow killer.
I’m getting the same issue here, for the last couple of months since switching to 2021.2. Can be any project using Burst.
Crossposting from the other thread discussing the same issue:
I can quite confidently say that Burst version 1.7.0-pre.1 solved whatever caused this issue.
I tried to recreate the error by repeatedly commenting and uncommenting lines of code inside and outside bursted code, to cause a recompilation.
Tried this on 1.7.0-pre.1 about 50 times, not a single time.
Changed back to 1.6.3, closed and reopened the editor - got the error on the second try.
2 Likes
Another possible workaround that does the trick without needing to fully restart the editor, if the save method does not work >
Try creating a new script, then deleting that script.
It seems anything that can trigger “Reload Scripting Assemblies” will solve the error.
Seems to happen when I save my scripts. after a while, the editor doesnt compile and I have to restart unity; Problem goes away after that. Am using latest release from Dec 11. 2021 on windows 10 2021.2.6f1
This works. I updated to 1.70-pre.1 for 2 days now, not seeing the error.
I found that when this happens, Unity is recompiling although reading above no idea if this is Burst related, but tend to have it installed. Saving in Visual Studio seems to trigger a recompile rather than a switchback does (on older versions?), but then if you save again while it’s recompiling you get this error. Wait a moment before resaves and it’s all gravy.
Hi, I have nearly the same problem but I’m not using Burst on my code, Burst is used by Universal RP and the pdb file that cause the error is Unity.RenderPipelines.Universal.Runtime.pdb.
The error happen only when I pull code changes from GIT.
Really weird error but really annoying too !
Unity 2021.2.3f1
Burst 1.6.3
Universal RP 12.1.1
Happens to me every 10 mins requiring constant editor restarts.
There is another thread that Unity has responded to, sounds like they are hoping to have this fixed in Burst 1.6.5.
Can confirm that I am having this issue on 2020.3.26f1. Really annoying to have to restart Unity every 15 minutes.