SwiftUI Map视图内存泄漏问题排查与修复求助

泄漏根源定位 #

结合你提供的代码，内存泄漏主要来自以下几个方面：

• UIKit与SwiftUI混合导航的生命周期脱节：通过UIKit的present方式展示地图页面时，包裹MapView的UIHostingController未被正确清理，导致SwiftUI视图及其关联资源无法释放。
• Map视图底层资源未解绑：SwiftUI的Map基于MKMapView实现，若未手动清理其绑定的状态或代理关系，会导致底层UIKit视图被强持有。
• 潜在的循环引用风险：如果MapVM存在未标记为weak的代理属性，会与MapVC/MapView形成循环引用，阻止对象销毁。

修复方案 #

1. 正确管理UIHostingController的生命周期 #

假设你的MapVC是用UIHostingController包裹MapView，需在控制器销毁时手动清理：

class MapVC: UIViewController {
    private var hostingController: UIHostingController<MapView>?

    override func viewDidLoad() {
        super.viewDidLoad()
        let mapView = MapView(viewModel: MapVM())
        hostingController = UIHostingController(rootView: mapView)
        
        addChild(hostingController!)
        view.addSubview(hostingController!.view)
        hostingController!.didMove(toParent: self)
        
        // 设置约束
        hostingController!.view.translatesAutoresizingMaskIntoConstraints = false
        NSLayoutConstraint.activate([
            hostingController!.view.topAnchor.constraint(equalTo: view.topAnchor),
            hostingController!.view.leadingAnchor.constraint(equalTo: view.leadingAnchor),
            hostingController!.view.trailingAnchor.constraint(equalTo: view.trailingAnchor),
            hostingController!.view.bottomAnchor.constraint(equalTo: view.bottomAnchor)
        ])
    }

    deinit {
        // 手动移除UIHostingController，释放SwiftUI视图
        hostingController?.willMove(toParent: nil)
        hostingController?.view.removeFromSuperview()
        hostingController?.removeFromParent()
        hostingController = nil
    }
}

2. 避免循环引用 #

• 确保MapVM的代理属性标记为weak，且协议继承AnyObject：

protocol MapVMDelegate: AnyObject {
    func dismissViewController()
}

class MapVM: ObservableObject {
    weak var delegate: MapVMDelegate?
}

• 在MapView的onDisappear回调中清理关联资源：

struct MapView: View {
    @State private var mapRegion: MKCoordinateRegion = MKCoordinateRegion(center: CLLocationCoordinate2D(latitude: 51.507222, longitude: -0.1275), span: MKCoordinateSpan(latitudeDelta: 0.5, longitudeDelta: 0.5))
    var viewModel: MapVM?

    var body: some View {
        VStack(alignment: .leading) {
            Text("Map")
                .foregroundStyle(.black)
            Map(coordinateRegion: $mapRegion, interactionModes: [.zoom, .pan])
                .frame(height: 300)
                .cornerRadius(10)
                .clipped()
        }
        .onDisappear {
            viewModel?.delegate = nil
            // 重置状态，帮助SwiftUI释放资源
            mapRegion = MKCoordinateRegion(center: CLLocationCoordinate2D(latitude: 51.507222, longitude: -0.1275), span: MKCoordinateSpan(latitudeDelta: 0.5, longitudeDelta: 0.5))
        }
    }
}

3. 改用SwiftUI原生导航（推荐） #

放弃UIKit的present方式，用SwiftUI原生导航管理生命周期，自动处理视图销毁：

struct HomeView: View {
    @ObservedObject var viewModel: HomeVM
    @State private var showMapView = false

    var body: some View {
        NavigationStack {
            ZStack {
                Color.white
                ScrollView(.vertical, showsIndicators: false) {
                    ZStack {
                        Color.primary.opacity(0.05)
                        VStack {
                            HomeHeaderView(location: "A123, North Street, Southern West")
                            HomePropertisView()
                                .onTapGesture {
                                    showMapView = true
                                }
                            RecommendedCardContainerView()
                            Spacer()
                        }
                    }
                    .ignoresSafeArea(.all, edges: .bottom)
                }
                .clipped()
            }
            .navigationDestination(isPresented: $showMapView) {
                MapView(viewModel: MapVM())
            }
        }
    }
}

4. 封装原生MKMapView替代SwiftUI Map #

若SwiftUI的Map仍存在泄漏，直接封装原生MKMapView手动管理资源：

struct MapView: UIViewRepresentable {
    @Binding var mapRegion: MKCoordinateRegion
    var viewModel: MapVM?

    func makeUIView(context: Context) -> MKMapView {
        let mapView = MKMapView()
        mapView.delegate = context.coordinator
        mapView.setRegion(mapRegion, animated: false)
        return mapView
    }

    func updateUIView(_ uiView: MKMapView, context: Context) {
        uiView.setRegion(mapRegion, animated: true)
    }

    func makeCoordinator() -> Coordinator {
        Coordinator(self)
    }

    class Coordinator: NSObject, MKMapViewDelegate {
        weak var parent: MapView?

        init(_ parent: MapView) {
            self.parent = parent
        }

        func mapView(_ mapView: MKMapView, regionDidChangeAnimated animated: Bool) {
            parent?.mapRegion = mapView.region
        }
    }

    static func dismantleUIView(_ uiView: MKMapView, coordinator: Coordinator) {
        // 手动解绑代理，避免循环引用
        uiView.delegate = nil
    }
}

替代实现思路 #

• 复用Map视图实例：将MapView放在父视图中，通过opacity或hidden控制显示，避免重复创建实例：

struct HomeView: View {
    @ObservedObject var viewModel: HomeVM
    @State private var showMap = false

    var body: some View {
        ZStack {
            ScrollView(/* 原内容 */)
            
            if showMap {
                MapView(viewModel: MapVM())
                    .transition(.opacity)
                    .onTapGesture { showMap = false }
            }
        }
    }
}

• 使用第三方地图库：若官方Map视图问题无法解决，可尝试Mapbox、Google Maps的SwiftUI封装库，这类库通常有更完善的内存管理机制。

内容的提问来源于stack exchange，提问作者Shivaditya kr