Textures/Mats don't unload from memory if I load a new texture before unloading previous one.

Graphics Shaders & Materials
1

In a sample texture swapping project I created, the textures don’t unload in memory (checked with build) if I load a different texture first. Here is the code where I release and then load a new texture, which causes a delay where the material has no texture:

    private IEnumerator SetTextureInternal(int texIndex)
    {
        if (_currentTextureHandle.IsValid())
        {
            Addressables.Release(_currentTextureHandle);
        }

        var textureReference = _textureReferences[texIndex];
        _currentTextureHandle = textureReference.LoadAssetAsync<Texture2D>();

        yield return _currentTextureHandle;
        _skinMaterial.mainTexture = _currentTextureHandle.Result;
    }

This code above works and the previous texture is unloaded from memory.

However, I want the swap to be seamless, so when I change it to load a new texture first and then release the previous one, the texture stays in memory even though there is no reference to it.

    private IEnumerator SetTextureInternal(int texIndex)
    {
        if (_currentTextureHandle.IsValid())
        {
            _pastTextureHandle = _currentTextureHandle;
        }

        var textureReference = _textureReferences[texIndex];
        _currentTextureHandle = textureReference.LoadAssetAsync<Texture2D>();

        yield return _currentTextureHandle;
        _skinMaterial.mainTexture = _currentTextureHandle.Result;

        if (_pastTextureHandle.IsValid())
        {
            Addressables.Release(_pastTextureHandle);
        }
    }

Is this a bug? I’m not sure what I’m doing wrong or what is causing the reference to stick around in memory. Calling Resources.UnloadUnusedAssets doesn’t clear it from memory either. According to the Addressables profiler the counter for the past addressable was released correctly as well.

2

Issue with partially unload an asset. I think they fix that in 1.3.3 - I didnt try that but saw that one line there.

3

I’m working in 1.3.8, and I don’t see any references to the textures in the profiler, even though they are still loaded. I don’t think this is the same bug.