At random times, sometimes after recompiling code, sometimes after modifying prefabs, sometimes after updating scenes, the spine-unity-editor.dll processing will start and last for a couple of minutes.
Is there any workaround or any way to speed up this processing?
During the processing I've noticed via the Task Manager on windows that the HDD usage spikes to 100%
To address the long loading times due to the spine-unity-editor.dll processing in Unity, you can try a few approaches to potentially speed up the process. First, ensure that you are using the latest version of the spine-unity runtime, as updates often include performance improvements and bug fixes. You can update the spine-csharp, spine-unity, and spine-unity-examples packages via the Unity Package Manager. Additionally, check if there are any unnecessary assets or scripts that could be optimized or removed to reduce the processing load. If the issue persists, consider profiling your project to identify specific bottlenecks or memory leaks that might be contributing to the high HDD usage.
Some of the ppl in our dev team using Unity on MacOS and do not seem to be experiencing this, seems to be a windows-only thing.
We've encountered such an issue on some Unity versions, especially when connecting the debugger, but not on others. Which Unity Editor version are you using?
Our project uses Unity 2022.3.21f1, while I do sometimes connect a debugger, most of the time it is not active or "connected"
@kb_z Thanks for the info. Unity 2022.3 was also exactly the version where the long wait times occurred when connecting the debugger, other versions (older as well as newer) seemed to not have this issue. So I'm afraid we can't do much about it on our end, on the positive side this issue is fixed automatically as soon as you switch to another Unity version in the future.
One more thing that you could try is whether changing the Project Settings Editor - Enter Play Mode Settings Reload Domain and Reload Scene changes anything on your end.
