Compliation never ends and hogs CPU to 100%

[plotinus]

For some weird reason I can't figure out my version of Synthesis starts compiling, but never ends.
I once let it run for an entire night just to see if it was just slow.

The problem appeared a few weeks ago and I have done the following to try to resolve it:

1. Followed the instructions in the thread for how to add Synthesis to the antivirus exclusion list.
2. Let it run for a long while.
3. Downloaded another wabbajack list and started Synthesis once to see if another instance of Synthesis could compile and be ready to start patching. It compiled as it should with no issues.
4. Disabled specific packages and tried to restart compilation one at a time.
   
5. Upgraded to latest beta version of Synthesis.
6. Downgraded to latest official release (0.32.1 at the time of writing).

I have not yet tried to downgrade even further because I suspect some shenanigans on my own system.

Which is why I tried and succeeded with compiling with the Eldergleam wabbajack list.

I have worked..... a lot and for a long time on my current list and I was going through various issues with the Wabbajack compiling when I suddenly got this headache to solve on top of it.

Have anyone else encountered this?
Any suggestions?

[Noggog]

I would check out the profile settings here:

Can dial the num processors down to 1-2 and see if it does better for you. Might take long on the first startup (you got lots of patchers to download + compile), but after that it should be quick on subsequent opens

Also, maybe try nuke the %temp%/Synthesis folder. This will force it to redownload the patchers and recompile from scratch, which might help if somehow you got the internals in a borked state one way or the other.

Let me know if adjusting that setting helps at all!

[plotinus]

I nuked and then restored the Synthesis folder. That helped. I could compile again.

Then issue reappeared. I saw @AidanMaskelyne's suggestion. But instead of uninstalling, then reinstalling, I selected to REPAIR the installation of .NET 8.0 SDK.

This resolved the issue for compilation.

Now I have mixed results regarding writing the patch after it is created after it has run successfully. It worked once, then on the next run it didn't.

I can copy output from %temp%/synthesis manually, but its still a headscratcher.

[AidanMaskelyne]

I had this issue and uninstalling and then reinstalling the .NET 8.0 SDK made it work for me.