Question Why does Addressables.Release destroy the result from WaitForCompletion in Windows Build?

I am using the recommended code structure (shown below) for loading Addressables with WaitForCompletion.

Code (CSharp):

1. void Start()
2. {
3.     //Basic use case of forcing a synchronous load of a GameObject
4.     var op = Addressables.LoadAssetAsync<GameObject>("myGameObjectKey");
5.     GameObject go = op.WaitForCompletion();
6.  
7.     //Do work...
8.  
9.     Addressables.Release(op);
10. }
11.  

My specific implementation is below:

Code (CSharp):

1.     public AudioClip LoadAudioClip(string key)
2.     {
3.         var op = Addressables.LoadAssetAsync<AudioClip>(key);
4.         AudioClip ac = op.WaitForCompletion();
5.         Addressables.Release(op);
6.         return ac;
7.     }

The code above works perfectly when running in Editor.

However, when I run the same code built for Windows Build and step through with Unity Debugger, the object (ac) is still populated correctly by the WaitForCompletion() line, but then ac is reset to null by the Addressables.Release() line.

If I comment out the Addressables.Release(op) line, then the code also works perfectly in Windows Build, so I know the setup of my Addressables and groups are correct. This makes no sense and is not a viable solution, since the Unity docs indicate that Addressables.Release is mandatory to prevent memory leaks. Any ideas?

 

Still stuck on this. For now I am having to build with Release line commented out. Has noone else experienced this?

 

Strictly speaking you only need to release the handle when the reference is no longer needed, though common practice is to get the ref, release the handle, return the reference.

Editor behaviour is different to build behaviour, in particular with addressables. By default in editor it's just using asset database. That said, this should be working.

So obvious first question, are you building your addressables before building your game?