Closed lawmicha closed 7 months ago
This issue was opened by a maintainer of this repository; updates will be posted here. If you are also experiencing this issue, please comment here with any relevant information so that we're aware and can prioritize accordingly.
We're in the process of migrating off AppSyncRealTimeClient package, which has the dependency on Starscream, over to URLSession here https://github.com/aws-amplify/amplify-swift/pull/3527 We should retest the memory leak scenario the changes from this PR
We plan to upgrade Starscream to 4.0.7. We can merge the upgrade commit on top of main
and release it as 3.2.0 https://github.com/aws-amplify/aws-appsync-realtime-client-ios/commits/main/ . The upgrade 4.0.6 will be replaced, we will not have a release which depends on 4.0.6
Amplify V2 (main
branch) no longer depends on AppSyncRealTimeClient package which had Starscream, it was replaced at v2.29.0 https://github.com/aws-amplify/amplify-swift/releases/tag/2.29.0
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
During this test I can see that there are memory leaks on web sockets: each
DataStore.start()
add new web sockets but old ones remain active. In my mind, we should use Starscream 4.0.6 which include this fix: https://github.com/daltoniam/Starscream/commit/d2a9549ea45018ef6802e3fe3c61490386a0ee8cOriginally posted by @gbitaudeau in https://github.com/aws-amplify/amplify-swift/issues/3259#issuecomment-1932387569