(Beta) JOBS might be the reason for regular frame rate drops

Astar beta 4.3.33, Unity 2019.4.11f1

In this scene, I have not used any PathFinding components yet but have a PathFinder.GridGraph fully setup and RVO Simulator.
There’re regular drops of frame rate that after some researches, I’ve finally found the source of problem.

As you can see in the screenshot, there’s a [1]CommandBuilder.StreamSplitter (Burst) that costs 37.35ms to complete. This is also [2] and because of that [3] has to wait for it to run that that wait cost 21.23ms.
All of this leads to Camera.Render costs 25.09ms to complete -> framerate drops.
This happens regularly, around 473 frames, ~7.83 seconds.

As how it is, this is JOBS, Burst problem and my project only use JOBS in Astar asset. So could you please take a look at this?


If it takes that long it seems like there must be a ton of debug lines being rendered? Is this the case?

You mean this is related to Line inside Astar, not Astar itself?
But relating to debug, every debug.log is inside #if UNITY_EDITOR and drawing of Line is in OnGizmosDraw only. So they should not be drawn in build, correct?
I’ll try to disable all debug options in Astar to see how it goes though.