Hi, the Jobs Debugger (Jobs->Jobs Debugger) has a bug. It is constantly reactivating after I deactivate it.
It then spams the console.
Any ideas how to stop it or is it in fact the way it supposed to be?
I would prefer to have control of the little bugger? lol
Any ideas?
It sounds like you were running into an issue we had where the JobsDebugger enabled/disabled setting was not persisting correctly. Thankfully, this was fixed earlier this year. Apologies for the annoyance!
The JobsDebugger feature detects and reports many classes of concurrency programming errors (e.g. race conditions, missing synchronization, etc.) which are traditionally very difficult to isolate and reproduce. The JobsDebugger can detect these issues statically, so rather than getting a catastrophic bug once every million runs, you get an error 100% of the time saying “hey, this code could potentially produce a catastrophic bug”. If it’s spamming the console, that’s usually a sign of a bug that should be fixed 
The JobsDebugger does introduce some performance overhead, so it should be disabled during performance testing to get more accurate measurements.
I had where the Jobs Debugger enabled/disabled setting was not persisting correctly.
This still happens ALL the time. I use Vegetation Studio Pro, which requires Burst and Jobs, but spams errors to the console if Jobs Debugger is on. I can turn it off, but the next time I start Unity, it’s on again. I really wish that a) somebody at A.W.E.S.O.M.E. would fix whatever is causing this, or b) that somebody at Unity would at least let me permanently turn the alarm off. Unfortunately, when I asked about this in the VSPro support Discord channel, I was told that the error is because the debugger can only process 5000 jobs in a frame, and VSPro often exceeds that.
I hate this kind of circular finger pointing:
Unity: “The debugger is showing a problem that needs to be fixed. We reactivate it to remind you.”
A.W.E.S.O.M.E.: “The problem is a Unity Jobs Debugger limitation, not a problem at our end. Just turn it off.”
Me: “I don’t care where the problem comes from. Can somebody just FIX IT.” 
Same issue here. I’m using VSP on Unity 2021 and every time i turn off the jobs debugger it gets re-activated when Unity next starts.
We’re getting just a warning spam though which doesn’t seem to be an actual problem?
JobDebugger dependency chain exceeds 5000 and is too expensive to validate.
Still getting this in 2021 LTS with Vegetation Studio Pro. Why is the world like this? How do you make a setting in your program that isn’t saved, and it gets through QA.