I would like to be able to collect profiling data on a physical device, say when I am going for a run, and later analyze that data using instruments.
Is there a way to do that?
Post not yet marked as solved
Hi, I'm using Instrument to profile my metal app, found a metric called display ( average frame time ) shows much longer than what expected. Is this truly the frame time ? Or did I misunderstand something ?
Post not yet marked as solved
I'm using instrument to profile my metal app, found there are more than one display devices shows on my view, I'm wondering what these display devices mean, thx .
Post not yet marked as solved
as you can see, gpu performance start earlier than gpu activity, i don't know why? thx
Post not yet marked as solved
this encoder happens to make gpu bubble, wondering what it is , and how to get rid of it, thx.
Post not yet marked as solved
It seems this ops shows up many times, can anyone tell me what it is plz.?
Post not yet marked as solved
Hello, I have a macbook for 1 year and I could never use Instruments Leaks. I always get these messages:
)
I have already reinstall my mac, I use the Xcode version 15, I tried to delete and reinstall Xcode. Nothing is working. Can somebody help me please?
Post not yet marked as solved
➜ ~ xctrace version
xctrace version 15.0.1 (15A507)
in my project, i use xctrace record command to attach exist app process, it high probability lead app hang, but attach is ok;
how can i solve this problem?
Post not yet marked as solved
Instruments in XCode 14 used to support CPU counters in A16 with iOS 16.x, but after I upgrade iOS to 17.1 and also XCode to 15.0.1, In "CPU Counters", it says "CPU Name: Unsupported" and thus I cannot choose "Sample by" events etc.
Found some link on this:https://stackoverflow.com/questions/77344529/is-latest-instruments-not-support-a17-pro-for-cpu-counters
Please help to confirm this is some known issue, and if so, how to fix it.
Thanks!
Post not yet marked as solved
Hi,
I have a few traces where I have samples for kernel (and other processes), yet kernel is always 0 for any CPU Counter selected. There are other processes with an equivalent number of samples where the counter values appear.
Perhaps there is a bit of 'art' to get the kernel counters to populate?
I am trying to understand the workload from the system perspective (not simply the narrower process perspective), and it would be helpful to have the counter values. I've tried running for extended durations, yet that doesn't seem to adjust the counted events. I've adjusted to include "High Frequency Sampling" to resolve issues with VMware counter collection. Yet..
I need help to enable counter values to appear for kernel.
Sam
Post not yet marked as solved
To run UI tests on actual devices, I use the following command to list devices possibly connected to my MAC:
xcrun xctrace list devices
As you know it shows a list of simulators and actual devices.
BUT it also shows actual devices NOT currently connected to my MAC. If they are not currently connected, I do not wish to see them.
Once a device is connected, it seems to always show up in the [== Devices ==] list.
Even after I disconnect the device it will still show up there. And my software thinks it can run tests on these devices.
Does anyone know how to get a correct list of devices which are currently connected to the MAC??
Post not yet marked as solved
I'm tracing a process, specifically focusing on the Metal device track, which records frames from other processes like Terminal, WindowServer, and sometimes processes that utilize the GPU.
I attempted tracing with all apps closed and only Instruments running. However, it also records traces for Instruments.
This behavior wasn't present in previous versions of Instruments. Was there a recent change in Instruments/Xcode 15.0.1? I cannot find any relevant information about this in the release notes either.
Is there a way to configure Instruments to record only the running process?
Post not yet marked as solved
Hi,
I am trying to debug an issue when running Profile within Xcode, the binary builds and is signed for release.
When I inspect the entitlements file, get-task-allow is always false.
I have the following settings that I have seen in the forums work for others but to no avail for our setup.
CODE_SIGN_INJECT_BASE_ENTITLEMENTS = YES
DEPLOYMENT_POSTPROCESSING = NO
Using manual signing setup, provisioning profile and certs are working fine and the binary launches fine on device.
However when it comes to pressing record in instruments, I get the following:
Permission to debug {app bundle ID} was denied.
Recovery Suggestion: The app must be debuggable and signed with 'get-task-allow'.
I don't have any other ideas on how to debug/troubleshoot this further.
Any help would be great, it's an old project so
Post not yet marked as solved
If I create a new project with the following code in main.swift and then Profile it in Instruments with the CPU Profiler template, nothing is logged in the Points of Interest category. I'm not sure if this is related to the recent macOS 14.2 update, but I'm running Xcode 15.1.
import Foundation
import OSLog
let signposter = OSSignposter(subsystem: "hofstee.test", category: .pointsOfInterest)
// os_signpost event #1
signposter.emitEvent("foo")
// os_signpost event #2
signposter.withIntervalSignpost("bar") {
print("Hello, World!")
}
If I change the template to the System Trace template and profile again, then the two os_signpost events show up as expected.
This used to work before, and this is a completely clean Xcode project created from the macOS Command Line Tool template. I'm not sure what's going on and searching for answers hasn't been fruitful. Changing the Bundle ID doesn't have any effect either.
Post not yet marked as solved
Hi! I have a macOS app and it uses around 2x more CPU when it's not launched by the Xcode debugger. This is not about build optimization or anything. I can use the exact same executable, and when I launch it directly by double clicking it in Finder it's uses 2x as much CPU as when I launch the executable through the Debug > Debug Executable... option in Xcode.
I did some CPU profiling in Instruments, and there is only one difference I could find so far when the app is launched by the Xcode debugger:
There is an entry in the trace named CA::Context::commit_transaction(CA::Transaction*, double, double) | Quartz Core. This entry always appears. But - If, and only if the app is not launched by the Xcode debugger, this entry has a child entry _dispatch_async_f_slow which itself has children that seem to be related to dispatch queue "introspection". It looks kind of like this:
v CA::Context::commit_transaction(CA::Transaction*, double, double)
v _dispatch_async_f_slow
> _dispatch_introspection_queue_item_enqueue_hook
_dispatch_trace_item_push_internal
dispatch_introspection_queue_item_get_info
> _dispatch_introspection_queue_item_enqueue
Now this alone doesn't account for the huge difference in CPU usage, but my best theory is that this dispatch queue introspection stuff is done all over the app, and cumulatively leads to the 2x slowdown.
I'm running
Xcode Version 15.1 (15C65)
macOS 14.1.2 (23B92)
M1 MacBook Air
If you have any clue how to prevent this slowdown when the Xcode debugger is not attached please let me know. Thank you so much!
Post not yet marked as solved
Hi, I noticed that when I use dyld activity instrument run duration is about 20s
Is it possible to customized it? I'd like to set it to something more, so when I start process I would able to capture event that could happen more than 20s after process start
thanks
Post not yet marked as solved
Steps to reproduce:
Open Instruments app
Settings
Select recording tab (Next to General)
Click Open Keyboard Shortcut preferences to produce the aforementioned error.
Profiler Version 15.1 (15C65) - Instruments
macOs 14.1.2 (23B92)
Thanks all.
Post not yet marked as solved
Hey, I'm learning Instruments (Xcode 15.1), and I've encountered a situation for which I haven't found an answer yet. I have an application that loads 12 large images, with the last one taking the most space at 147MB.
Instruments on the iOS 15 simulator correctly shows 21 allocations, as in the example from the book, because the last image is split into smaller parts due to poor optimization.
But if I run the same example on the iOS 17 simulator, I have even fewer allocations than loaded images.
And my question is whether memory allocation for large images is handled differently in iOS 17, or where can I read more about it?
Post not yet marked as solved
Instruments freeze when WKWebView is created
I create a very simple mac os application
If I create a WKWebView like this
"
(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
self.webview = [[WKWebView alloc] initWithFrame:NSMakeRect(0, 0, 500, 500)];
}
"
Then the instruments freeze when I record allocations
Why?
If I remove the creation of WKWebView, everything works fine
I'm using Xcode 14.2
Post not yet marked as solved
Hi,
I've run an Instruments network capture of our iOS app and the Points of Interest track lists faults due to undisclosed tracking domains. For example app-measurement.com which is used by Firebase causes the fault:
Fault: app-measurement.com is not listed in your app's NSPrivacyTrackingDomain key in any privacy manifest. It may be following users across multiple apps and websites to create a profile about users of apps that contact this domain.
However my PrivacyInfo.xcprivacy file contains (API and Nutrition info omitted):
NSPrivacyTracking: true
NSPrivacyTrackingDomains:
app-measurement.com
So I'm surprised the fault is still occurring.
Is it because the call is coming from a 3rd party SDK (Firebase)? I'll be removing this entry once a compliant Firebase SDK is released but figured it should still work.
I've checked that the IPA contains PrivacyInfo.xcprivacy, and that I'm able to generate a privacy report.
I'm using Xcode 15.0, iOS 17.1.