Insane Memory Usage when copying, moving or renaming assets
OS: Windows 10 64bit (was: Windows 8.1 Pro 64-bit)
Steps to reproduce:
Store Packages that produce this behaviour:
When you modify assets in this manner, every asset has to be loaded into memory. The reason behind this and the additional time taken during this process is that the Editor must check references to all of those assets. If a link was broken when moving a material(for instance), ANYTHING that references that material would need to have it re-assigned manually.
Massive move operations require this to be done for EVERY asset. I would recommend setting aside some time for something like this in the future. This is especially true if you're using source control as well.
answered May 08 '15 at 02:35 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here