Search Issue Tracker


Planned for 2019.1



Found in



Issue ID




Error message - Asset import did not unload metadata path. This will leak memory

Asset Importers


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)`

Comments (5)

  1. 4ac01c722a5c442aa98b739f64d3d3a0?d=mm


    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:

  2. E1e9a1145ad8c57f63522646efeed37a?d=mm


    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.

  3. 5e6391e6b9c8a1909b84cf52903dbac3?d=mm


    Jul 19, 2019 12:59

    Just saw this error after setting double sided shadows for a prefab within a very simple project

  4. Df6e86428e1d855b00b6734aa85bdefd?d=mm


    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.

  5. 0e9a020ba338eebfcd54845206d8ff1f?d=mm


    Mar 31, 2019 05:58

    Got this error while reimporting a Generic rig after exposing some transforms.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.