-
Re: "an error occurred trying to capture leaks data"
w3sip Apr 12, 2019 9:18 AM (in response to greay)I have the same error -- runs for a little bit, then errors out. Also, can't attach to a running process anymore.
What gives, Apple?
-
Re: "an error occurred trying to capture leaks data"
LaurieM44 Apr 15, 2019 12:04 PM (in response to greay)Same error for me here but for a macos app on xcode 12.2. I have the error "An error occurred trying to capture Leaks data" after a couple of seconds running in Instruments.
-
Re: "an error occurred trying to capture leaks data"
Dalzhim Apr 26, 2019 6:42 AM (in response to greay)I have experienced the same issue. Here are some more details :
Allocations instrument: Failed to attach to target: Failed to attach to target process.
Leaks instrument: An error occurred trying to capture Leaks data
Time Profiler instrument: Runs perfectly fine
One workaround I have used is to profile in debug rather than release by changing the scheme configuration : Edit Scheme > Profile > Info > Build Configuration.
-
Re: "an error occurred trying to capture leaks data"
ding0039 May 23, 2019 12:53 AM (in response to greay)Same error for me
-
Re: "an error occurred trying to capture leaks data"
dwarfland Nov 25, 2019 5:50 AM (in response to greay)Same here, two different MacBooks (Cataline GM and latest Cataline beta, respectively), Xcode 11.0, 11.1 and 11.2.1. Instrunments either "cannot attach" or "cannot load tracking library" or beachballs or it "runs" but the (macOS) app never shows (though the process in `ps`). Essentially Instruments is entirely and literally unusable, which is really annoying and a productivity problem. (Instrument has been getting bad for a while, but at least it stil *ran* in Xcode 9/10).
Wondering if Apple in 2019 is capable of touching any part of its software catalog without just breaking it beyond repair...