loading 4096 texture causes huge mono heap grow, with 2048 almost no offect on mono heap

Hi, i have noticed that loading huge custom file that represent compressed texture using UnityWebRequest and creating texture in runtime with it's byte data (using LoadRawTextureData) creates huge mono heap grow that cannot be released. here is the sample code:

Code (CSharp):

1. using (var downloadRequest = UnityWebRequest.Get(mainUrl))
2.             {
3.                 byte[] bytes= null;
4.                 yield return downloadRequest.SendWebRequest();
5.                
6.                 bytes= new byte[(int)downloadRequest.downloadedBytes - header];
7.                 Buffer.BlockCopy(downloadRequest.downloadHandler.data, header, bytes, 0, (int)downloadRequest.downloadedBytes - header);
8.                
9.                 texture.LoadRawTextureData(bytes);
10.                 texture.Apply(false, true);
11.                 texture.wrapMode = TextureWrapMode.Clamp;
12.                
13.             }
14.  

any ideas?

 

pearhaps the optional parameter (true) with GetTexture

Code (CSharp):

1. string url = "http://www.my-server.com/myimage.png";
2. using (UnityWebRequest uwr = UnityWebRequestTexture.GetTexture(url, true))

https://docs.unity3d.com/ScriptReference/Networking.UnityWebRequestTexture.GetTexture.html

 

why loading as bytes and not using the UnityWebRequestTexture?
and as sumpfkraut wrote, set nonReadable as true.

The wasm memory size is limited.
while some browsers on some platforms can contain large enough memory size for 2048*2048 image, 4096*4096 is too big.

The UnityWebRequestTexture know how to handle the texture on the JavaScript side, and if you set it as nonReadable, it won't load the byte data to the wasm memory.