Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
0
Found in
5.6.2p4
Issue ID
945175
Regression
Yes
[macOS] Memory usage increases significantly when using AssetDatabase.CopyAsset
Using "AssetDatabase.CopyAsset" function takes too much memory for every copied asset. If the assets are enough to take all the system memory, the Editor crashes which is user's real case.
Steps to reproduce:
1. Open user's attached project
2. Go to menu Test > CopyTextures.
3. Look in the Activity Monitor app (or any other memory tracker) that there are massive memory growths.
Result: a lot of memory is being used, if it takes all the system memory, the Editor crashes.
Reproduced with: 2017.2.0b9, 2017.1.0p5, 5.6.3p2.
Not reproduced with: 5.5.4p2.
Regression introduced in: 5.6.2p1.
Workaround: use FileUtil.CopyFileOrDirectory(srcPath, dstPath);
Note: not reproducible on Windows.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment