AmazonChimeSDK memory leak

[denizmersinlioglu]

Describe the bug We noticed memory leak in the AmazonChimeSDKDemo application (and also in our own implementation) originated from AmazonChimeSDK.

To Reproduce Steps to reproduce the behavior:

1. Open Demo Application
2. Join a meeting (lets say N times)
3. Leave the meeting (let say N times)
4. Open Memory report and see Screenshot1 (You should see increasing memory usage for every join-leave flow)
5. Open Memory Debugger and see Screenshot2

Expected behavior We expect all allocated objects to be deallocated as soon as we leave the meeting.

Logs Here is the memory leak trace from Xcode-Instruments: https://drive.google.com/drive/folders/1ANQNIOvHVX5Erb7Ooq5Oq7zUTKG92KkO?usp=sharing

Screenshots

1. 
2. 

Test environment Info (please complete the following information):

• Device: [e.g. iPhone6s]
• OS: [e.g. iOS14.3]
• Version AmazonChimeSDK: [e.g. 0.13.0]
• Version AmazonChimeSDKMedia: [e.g. 0.9.0]

Additional context 1.In our implementation, we were able to avoid DefaultVideoRenderView leaks by unbind the DefaultVideoRenderView from the audioVideoFacade. 2.The following properties may cause a retain cycle:

• AmazonChimeSDKMedia -> AudioClient -> @property (nonatomic, retain) NSObject <AudioClientDelegate> *delegate;
• DefaultAudioClientObserver->private var audioClient: AudioClient

[piv199]

Could you please check for retain cycles, because when I just create DefaultMeetingSession and deallocate it - I have some leftovers in memory... Basically, I'm experiencing quite the same as @denizmersinlioglu .

[denizmersinlioglu]

@hokyungh @zhinang-amazon Thanks for your great effort. Is there any update on MediaSDK layer memory leaks?

[hokyungh]

@denizmersinlioglu sorry for late update. v0.16.0 should contain some memory leak fix in the SDK layer. It doesn't solve all the issue, but it should some memory fix in the SDK layer. We'll work to resolve rest of memory leak fixes on the MediaSDK layer.

[georgezy-amzn]

Closing this due to inactivity. Please reopen or submit a support case if this is still an issue.