best practices for Memory Leak in Custom NSDocument Implementation on macOS 13.6
This might be a silly question, but I'm a bit lost with I'm getting frustrated with I've searched everywhere and can't find a clear answer..... I'm working with a memory leak when using a custom NSDocument subclass in my macOS 13.6 application. After saving and closing documents multiple times, I notice that the memory usage continues to rise. I've implemented the required methods like `dataOfType:behavior:` and `read(from:)`, but I'm not sure if I'm properly managing the references to the document's data. Here's a snippet of my `dataOfType:` implementation: ```swift override func data(ofType typeName: String) throws -> Data { let data = try JSONEncoder().encode(self.documentData) return data } ``` And for reading: ```swift override func read(from data: Data, ofType typeName: String) throws { self.documentData = try JSONDecoder().decode(DocumentData.self, from: data) } ``` I’ve also ensured that I’m not retaining unnecessary references in my model objects. I ran the Allocations and Leaks instruments in Xcode, and it appears that some objects are not being deallocated after closing the document. I suspect it might be related to delegates or notifications that I might not be removing properly. Here’s how I set up my observers: ```swift NotificationCenter.default.addObserver(self, selector: #selector(handleNotification), name: .someNotification, object: nil) ``` After closing the document, I call: ```swift NotificationCenter.default.removeObserver(self) ``` Yet, the memory doesn't seem to drop. I've also checked for retain cycles using the Memory Graph Debugger, but nothing stands out as problematic. Any insights or suggestions on what I might be missing here would be greatly appreciated! My development environment is Windows. What's the best practice here? Is there a better approach?