Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2020.3
2020.3.1f1
Issue ID
1345444
Regression
No
AssetPostprocessors loads all Assets of the same type into Memory at once
Reproduction steps:
1. Open user attached Project
2. Check Allocated memory Before and After Asset Import in the Console
Expected result: The Memory used doesn't increase significantly
Actual result: The Memory used had increased by about 811 times
Reproducible with: 2020.3.6f1
Could not test with: 2019.4, 2020.3.14f1, 2021.1, 2021.2, 2022.1 (Reproduction requires modified Editor)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a10
Added a new Editor Preference to disable the Bump map check processing done in ModelImporterPostProcessor .