Hi,
I work mainly on an Athlon PC with Unity 2022.3.15 where the editor is very stable.
I am testing my project in mirror on 2 other PCs, a tower and a laptop, both Intel with 16GB of ram and the editor crashes constantly on these PCs.
Is Intel cursed?
Have you noticed frequent crashes with this CPU?
You can’t make such a rough assessment. Every PC is different. 
Check the editor.log for details about the crash. Try to find out if it’s always the same thing that’s crashing.
Since you’re on 2022.3.15 consider upgrading, we’re at patch 2022.3.50 by now! That’s 35 bugfix updates you don’t have, and yours may be one of those that have been fixed.
Also try deleting the Library (details in here). Especially if you a) just copied the entire project including the Library to those PCs (never share the Library) or b) share the project through some cloud sync tool - in that case: DON’T! Cloud sync has the potential to destroy assets in your project or even the entire project irrevocably.
Other than that, be sure to install the latest graphics drivers.
2 Likes
Indeed, I had not deleted the library before the copy, but it will not work because I am making a mirror copy. So it is the same library.
But thanks for the advice.
What do you mean by that?
I thought you meant the Mirror networking framework.
Depending on how you “mirror” the project, the result may be corrupted projects especially if this is an automated, ongoing process ie synchronizing the projects while you work in the source project respectively merely having it open suffices. That kind of thing will likely create corrupt copies due to files being locked and thus not mirrored, and mirroring temporary files that the remote editor instances don’t expect and get confused by.
I use SyncBackFree for all my backups. And I use the “Mirror” option for my Unity projects.
The important bits are:
- Do you trigger the mirroring manually? It must not run scheduled or continuously.
- Do you close the project before mirroring runs? Mirroring should not be done with a currently open project.
Basically both are because of the same problem: possibly locked files and thus incomplete mirroring.
The Library should also be excluded along with Temp, Obj, Logs, Builds, Recordings and *.sln and *.csproj in the root, if the tool has exlusion filters. See Unity .gitignore defaults.
If you make any changes at all in the remote projects, use source control. Absolutely no way around it. Backup tools don’t merge conflicts.
SyncBackFree forces you to close the project before copying.