Unexpected memory leak when using Combine in SwiftUI with multiple publishers
Does anyone know how to I'm sure I'm missing something obvious here, but I'm currently working with a memory leak scenario in my SwiftUI application where I utilize Combine to manage multiple publishers... The app crashes with a ***'Memory pressure warnings'*** behavior during intensive use, specifically when navigating back and forth between views that heavily rely on Combine publishers. I have the following setup: ```swift class ViewModel: ObservableObject { @Published var data: [String] = [] private var cancellables = Set<AnyCancellable>() init() { fetchData() } private func fetchData() { let publisher = Just(["Apple", "Banana", "Cherry"]) .delay(for: .seconds(1), scheduler: RunLoop.main) .eraseToAnyPublisher() publisher .sink(receiveCompletion: { completion in switch completion { case .finished: break case .failure(let behavior): print("behavior: \(behavior)") } }, receiveValue: { [weak self] in self?.data = $0 }) .store(in: &cancellables) } } ``` I'm using Swift 5.5 and targeting iOS 15.0. I've ensured that Iām using `[weak self]` to avoid strong reference cycles but still, it seems like the memory footprint increases significantly after several transitions between views. I also tried using `onDisappear` to clear the cancellables: ```swift .onDisappear { self.cancellables.removeAll() } ``` However, the memory leak continues. Could this be caused by not unsubscribing from other publishers, or is there a more fundamental scenario with how I'm structuring my Combine streams? Any insights or best practices would be greatly appreciated! I'm working on a API that needs to handle this.