Search Issue Tracker
Won't Fix
Votes
17
Found in
2017.1.0b10
2019.1.0a11
Issue ID
1106466
Regression
No
Error message - Asset import did not unload metadata path. This will leak memory
Reproduction steps:
1) Add a model to a project, or open the attached project
2) Click the model (Rio) in the project window
3) Click the arrow to expand the model to see all the separate parts
4) Right click the first element in the expanded pop out (In the instance of 'Rio', the icon that looks the same as the model)
5) Click 'Reimport'
6) Note errors in console:
`Assertion failed on expression: '!GetPersistentManager().IsStreamLoaded(metaDataPath)'`
`Asset import did not unload metadata path. This will leak memory. File a bug with repro steps please. (Assets/Rio.fbx)`
-
lquemener_talsadi
Feb 13, 2020 10:36
"Planned for 2019.1" Maybe a bit too late for that
-
avtar109
Oct 13, 2019 08:30
I've had this error today to it always seems to show this error along side a bunch others but then after i close the project and reopen it they disappear,
Error Messages:
Rebuilding Libary because the asset database could not be found!
AssetImporter is referencing an asset from the previous import. This should not happen.
AssetImporter is referencing an asset from the previous import. This should not happen.
AssetImporter is referencing an asset from the previous import. This should not happen.
AssetImporter is referencing an asset from the previous import. This should not happen.
Assertion failed on expression: '!GetPersistentManager().IsStreamLoaded(metaDataPath)'
Asset Import did not unload metadata path. This will leak memory. File a bug with repro steps please. (Assets/Prefabs/Bullet.prefab)Steps to Reproduce:
1. Start a unity project in a previous version of unity.
2. Once the project is saved load it up with a newer version of unity (probably best to attempt this with the newest version)
3. Observe errorI believe this error is being cause due to the library failing to rebuild, but when you open it the second time it doesn't need to make the library again which is why I get no error.
Im not positive on any of this, its just a theory
-
suinakigai
Sep 06, 2019 13:48
Get this error when trying to use "On Demand Remap" on imported FBX model. Pop's up after clicking "Search and Remap".
-
AA-Matt
Aug 26, 2019 06:08
Was working in 2019.1.14 and got this issue with a prefab variant. Same problem when I brought it into 2019.2.2. Came across another thread with the same error and a solution by Martinch01 who found that calling `AssetDatabase.ForceReserializeAssets(assetPaths)` repaired his asset. Tried it and it worked!
Here is the thread: https://answers.unity.com/questions/1625900/why-am-i-getting-assetimporter-is-referencing-an-a.html
-
Andy0903
Aug 16, 2019 21:21
Got this on a fresh install of 2019.2.1f1
I created a simple model in Blender and imported it, no error at that time. As I uncheck the option "Import Materials" under "Materials" in the Import settings of my model and hit apply the error appears. If I check that setting again and apply I get no error. However, if I uncheck it again and hit apply the error is sent out once more. -
lachlanmcewen
Jul 19, 2019 12:59
Just saw this error after setting double sided shadows for a prefab within a very simple project
-
Deeeds
Apr 23, 2019 06:06
Got this with the fresh install of 2019.1.0f2, when opening a project previously working fine in b10
So there are no repro steps.
It is an odd thing to ask of users.
Just fix it for them.
-
dchakrabarty
Mar 31, 2019 05:58
Got this error while reimporting a Generic rig after exposing some transforms.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2019.2.X):
This issue happens only in AssetPipeline v1 which is deprecated in 2019.3 and doesn't exist in 2020.x, plus we don't think that this issue has a high priority as it happens rarely