Question InitializationObjectsOperation persists in Profiler

Doing some tests using Addressables and I noticed that the InitializationObjectsOperation won't leave the profiler? I instantiate two addressable assets then release them and go back to an empty scene (which is not an addressable asset) The reference count for my instantiated objects turns zero and eventually disappears from the profiler but the InitializationObjectsOperation still has a ref count of 1 and doesn't leave the profiler ever (unless I press clear). Although when I do go back to the scene where it instantiates two addressable assets, its ref count is still 1 and doesn't increase. Anyone has an idea what this operation does?

 

Did you ever figure this out?

Noticed the same thing in my project

 

Haven't figured this out We just left it as it is since it doesn't increment anyway.

 

Yeah.. it is annoying..

Here is the code to reproduce if anyone at Unity can look at it:

Create this component, add it to game object. Add any addressable sprite to it.
You will see the event viewer has a lingering InitializationObjectsOperation even after everything has been released.

Reproduced it in 2019.3 LTS (1.8.5) and 2020.3 LTS (1.13.1)

Code (CSharp):

1. public class AddressableTester : MonoBehaviour
2. {
3.     public AssetReferenceSprite SpriteToLoad;
4.     void Start()
5.     {
6.         var handle = SpriteToLoad.LoadAssetAsync();
7.         handle.Completed += operationHandle =>
8.         {
9.             Addressables.Release(handle);
10.         };
11.     }
12. }

 

I'm having the same issue on 2020.3.16f...

 

I'll just go ahead and bump this thread as I just noticed the same issue in my project and I don't know where it is coming from and how to get rid of it (it does not appear when testing in the editor, this was with a build).

 

Still persists on 2021.3.11f1 LTS. Bump.
Having issues on same thing as code to reproduce above: Just load loading asset while Start() at starting playmode.
When I unload an asset and load it later - it throws me

Attempting to load AssetReference that has already been loaded. Handle is exposed through getter OperationHandle

While other assets that are loading by exactly same method are ok to unload + load.