Memory leak when using AppSyncClient

[awslabs]

Memory leak when using AppSyncClient

[ifabijanovic]

I'm afraid it's worse than this - the client itself is in a retain cycle from initialization and it cannot be released (on logout for example). Simply doing something like this (using code from sample):

let databaseURL = URL(fileURLWithPath:NSTemporaryDirectory()).appendingPathComponent("events-app-db")            
let appSyncConfig = try AWSAppSyncClientConfiguration(appSyncClientInfo: AWSAppSyncClientInfo(), databaseURL: databaseURL)
self.appSyncClient = try AWSAppSyncClient(appSyncConfig: appSyncConfig)
self.appSyncClient = nil

Will not release AWSAppSyncClient, which in turn won't release a whole graph of objects including an SQLite Connection.

[joelmbell]

This is affecting us as well, hoping that MR can get merged into a new version soon. We currently have a bug where mutations are attempting to send after a user has logged out. AppSyncClient should be nil'd out before that happens but due to the retain cycle we can't stop it from sending stored mutations if they exist

[palpatim]

Hi folks,

We've recently added tests to ensure that we do in fact release appSyncClient when the owner sets to nil.

4936c31

It should be fixed as of 2.9.1.

[stale]

This issue has been automatically closed because of inactivity. Please open a new issue if are still encountering problems.