我目前用的Wwise版本是2019.2.14，我在测试的过程中发现存在内存泄露的情况，对于Wwise中小于约2MB的Bank，在卸载之后，Reserved Memory却没有下降对应Bank的大小。（实际上，在我参与过的好几个不同Wwise版本的项目，都存在这种情况）
对于这个问题，我想问一下，这是Wwise官方在Wwise中底层设置了一个内存缓存机制吗？对于Bank而言，限定某一个大小的阈值，来保留某一些Bank在Reserved Memory中存在？但是在我所接触到的很多项目中，少于这个阈值（2MB）的Bank数量是很常见的，许多游戏会把Bank大小尽可能解耦、压缩，这就导致了内存泄露出现地很频繁。
所以，我想问下，关于这个问题，可以怎么做来遏制这个问题？
1.通过人为在代码中更改缓存阈值来减缓吗？这似乎也只能做到减缓，并不能完全解决这个问题。
2.能不能告知现在有哪些版本不存在我所说的这种情况？（我在查找不同版本文档时，关于这一点的说明很少。）
3.又或者只能通过合并那些较小的Bank来达到Wwise设定的缓存阈值解决？
十分感谢您的阅读，盼望得到您的回复！
The Wwise version I am currently using is September 14th, 2019. During testing, I found a memory leak. For banks with Wwise size smaller than approximately 2MB, after uninstalling, the Reserved Memory did not decrease the corresponding bank size. (In fact, this situation exists in several different versions of Wwise projects that I have participated in.)
For this question, I would like to ask, is this a memory caching mechanism that Wwise has officially set up at the bottom level in Wwise? For banks, setting a threshold of a certain size to preserve the presence of certain banks in Reserved Memory? However, in many projects I have been exposed to, it is common for the number of banks to be less than this threshold (2MB). Many games try to decouple and compress the bank size as much as possible, which leads to frequent memory leaks.
So, I would like to ask, what can be done to curb this issue?
1.Does it slow down by manually changing the cache threshold in the code? This seems to only be able to slow down and cannot completely solve the problem.
2.Can you tell me which versions currently do not have the situation I mentioned? When I am searching for different versions of documents, there is very little explanation on this point.
3. Or can we only achieve the cache threshold set by Wwise by merging smaller banks?
Thank you very much for reading and looking forward to your reply!