'audio' memory leak

Which is impressive, because I have 0 audio files in this project.

 

Ok woke up this morning, first time hitting play didn't happen, 'only 2.5GB' of audio memory was allocated.
But hitting play the second time audio memory just started growing slowly, a few MBs per frame in the audio category.

This is in 2020.2.0a19. The scene I'm in is mostly just 1 large subscene with about 9000 objects with hdrp and hybrid renderer v2.
I'm not sure how to create a small repo for this, but I can get you some profile data.

The memory profiler doesn't really match Unitys memory usage






It doesn't look very useful to me but if you want the actual memory profile data, I'll upload it via bug report for privacy reasons.

-edit-

every time i hit play in editor, 'audio' memory in profiler jumps about 500MB

 

Started a new play, let it idle for 15min; 5GB more memory used but the memory profiler snapshot is nearly the same.

 

No, I first noticed it because I left scene running in background by accident, system started becoming sluggish and I looked and had 20GB+ of memory allocated.
The project as very little of my own code; I was playing around with hdrp (and hybrid renderer v2).

By default I have audio profiler disabled but I enabled it after seeing huge garbage though it reported pretty much nothing as you'd expect.

So I feel like I should have realized this, but somehow I did not know this about the memory profiler (and you've just helped me tremendously with a project at work).

I loaded up the same project, but couldn't really get it to 'leak' memory again in the short time I tested it but it was jumping upwards of about 500MB memory every time I entered play mode (with the audio memory value was going up in the profiler).

Comparing 2 snapshots between 4GB (first play) and 6.5GB (about 7th play) the primary areas of new allocations were

A lot of blocks of this (one picked at random)


And this


And this


And a few blocks of this


And it all seems to be allocating to the Audio

 

Maybe this view helps? (this was the second profile so has some of the profiler data)

 

@MartinTilo
Other than native plugin, there is also a bug on the onaudiofilterread method implementation that allocate memory on every call. It's there since around Unity 5 and has never been fixed, because the issue itself was introduced as a workaround for a scenario that would lead to a crash.
Maybe this is related to that? The bug number is 784161 and is open since 2016...

 

Not fixed, I just checked around a month ago on 2019.3 or .4.

EDIT
Last time I checked only on the Unity profile, maybe what I see on the profiler is not memory allocated from the audio anymore, I should check with the Xcode profiler, it's more clear there.

 

Nah I have no plugins/dlls in the project at all other than ones that may be included in official Unity packages.

Just a random observation from examining memory on an xbox app the other day, but could it be 'Allocator' memory (nativearray, etc) as this didn't seem to show up for me without looking at raw data on memory profiler.

 

Yes I'm using DOTS. The original post was mostly a large subscene of (12k) pure renderers; and that was about it.

I can't seem to replicate the growing memory issue anymore. My memory is sitting much lower even with the same scene loaded. This project has been updated to the new version of entities/hybrid since the original post so that could have fixed it, or something else i randomly tweaked fix it. Such is the life of software development...




However memory being reported as audio still exist, but it sounds like you have a fix for that in the works.