Every time I run my project in Unity, I see a ton of Wwise: Insufficient memory in pool: Monitor errors. Many many many errors.
I followed these steps -- to connect the Wwise advanced profiler to my Unity build. I can plainly see that the Monitor pool has 249.6 KB reserved, and has used 249.6 KB -- so there is no memory left. I am also seeing in my errors an "Attempted alloc size" of 29 bytes (when running in Unity) and sometimes 1024 bytes (when running with the Wwise profiler attached). It is clear the Monitor pool is maxed out. Why is it not auto-increasing? How do I increase it?
Does anyone know how to increase the size of the Monitor memory pool in Unity?
I note here that -- when calculating memory usage -- one should "Subtract the size of the Communications, Monitor, and Monitor Queue memory pools. These pools contain debug-only allocations which are not created in the Release version. Subtracting the size of these pools should give you a good idea of the release-version memory usage." My questions to this are:
- how to make a Release version? no matter how I bulid in Unity, I get these errors, and don't see a "Release" setting. does any one know where this is?
- how is someone supposed to debug with these errors? I would like to be able to make clean, error-free Debug builds.
My deep Google search around this issue found this page
-- with a CryEngine-specific s_WwiseMonitorMemoryPoolSize setting. Despite much searching through the Wwise/Unity code base I cannot find such a thing for Unity.