SwiftUI中MapKit的MKDirections.calculate()调用出现内存泄漏问题

你遇到的MKDirections.calculate()内存泄漏问题，核心源于两个关键问题：

• 局部创建的MKDirections实例在异步回调后未被主动清理，MapKit内部残留未释放的资源
• 闭包捕获逻辑和CLLocationManager生命周期管理不当，加剧了内存异常

关键修复点 #

1. 主动管理MKDirections生命周期：避免用局部变量创建实例，改用可持有的对象管理，回调完成后调用cancel()并置空引用，强制释放资源
2. 安全处理可选值：对deviceLocation这类可选值做判空处理，既防止崩溃也减少潜在内存异常
3. 规范CLLocationManager持有方式：局部创建的CLLocationManager会被立即释放，导致权限请求回调失效，需用@StateObject或ObservableObject长期持有

修正后的代码示例 #

先创建专门管理地图逻辑的ObservableObject：

import SwiftUI
import MapKit

class MapDirectionManager: ObservableObject {
    private var directions: MKDirections?
    private let locationManager = CLLocationManager()
    
    func calculateDistance(completion: @escaping (CLLocationDistance, String) -> Void) {
        // 安全获取设备位置
        guard let deviceLocation = locationManager.location?.coordinate else {
            completion(0, "无法获取设备位置")
            return
        }
        
        let request = MKDirections.Request()
        request.departureDate = Date()
        request.arrivalDate = Date().addingTimeInterval(1)
        request.source = MKMapItem(placemark: MKPlacemark(coordinate: deviceLocation))
        request.destination = MKMapItem(placemark: MKPlacemark(coordinate: CLLocationCoordinate2D(latitude: 36.073, longitude: -79.792)))
        request.requestsAlternateRoutes = true
        request.transportType = .automobile
        
        directions = MKDirections(request: request)
        directions?.calculate { [weak self] response, error in
            defer {
                // 无论回调成功失败，都立即清理资源
                self?.directions?.cancel()
                self?.directions = nil
            }
            
            if let error = error {
                completion(0, error.localizedDescription)
                return
            }
            
            // 实际业务中可从routes获取真实距离
            let distance = response?.routes.first?.distance ?? 0
            completion(distance, "")
        }
    }
    
    func requestLocationPermission() {
        if locationManager.authorizationStatus != .authorizedWhenInUse && locationManager.authorizationStatus != .authorizedAlways {
            locationManager.requestWhenInUseAuthorization()
        }
    }
}

再在ContentView中调用：

struct ContentView: View {
    @State var myText: String = ""
    @StateObject private var directionManager = MapDirectionManager()
    
    var body: some View {
        VStack {
            Text(myText)
        }
        .padding()
        .onAppear {
            directionManager.requestLocationPermission()
            directionManager.calculateDistance { distance, error in
                myText = error.isEmpty ? String(format: "距离：%.2f米", distance) : error
            }
        }
    }
}

补充说明 #

• [weak self]捕获避免循环引用，保证MapDirectionManager能被正常释放
• defer块确保回调结束后一定会清理MKDirections实例，切断MapKit内部的资源持有链
• 将CLLocationManager作为单例持有在Manager中，避免局部释放导致的权限请求丢失

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