Post

Replies

Boosts

Views

Activity

Reply to Potential memory leaks in CLLocationUpdate.Updates
Thanks for your swift reply. Sorry for small delay on my side. I have been preparing the so called Test Project (see (2) below) Correct - the leaks I attached come from the Instruments / Leaks tool. I am not sure what you exactly mean by "Test project". I assumed you wanted to have a new, simple project containing the core functionality to reproduce the leaks issue. I created such basic-functionality project, stripping off all unnecessary elements and code, just leaving the core: location tracking. I kept the structure of my app though (so it is not as simple as it could be for such functionality), as it might help to investigate the case, I think. And finally YES, I observe the same leaks in this test project as in my main project - 5 leaks every time I press "<back" button, which stops location tracking. In the Leak tool, when I choose any of the leaks, and then choose in the right panel the bold marked Stack trace "closure #1 in LocationsHandler.startLocationUpdates()" I get this code marked: Task() { do { self.updatesStarted = true 5x 336 bytes let updates = CLLocationUpdate.liveUpdates() for try await update in updates { I do not know how to share the link to my project though.
Oct ’24
Reply to Xcode Canvas Simulator cause multiple diagnosticd processes to run and 100% CPU
I have the same (or similar) issue. SpringBoard getting over 100% CPU load and the computer is overheating when I launch Xcode. Workaround, which seem to work quite well, is to Force Quit SpringBoard in Activity Monitor every time I start Xcode session. Then the process is reinstated, but with the normal usage. I run Xcode: Version 15.0.1 (15A507) My computer: MacBook Air M1, 16GB, macOS Sonoma, 14.1.1
Nov ’23