Jed Fox

@jedfox
374 Followers
214 Following
230 Posts
he/him. views are my own etc etc. it’s spelled ‘evertrue.’ Instruments/profiling tools @ Apple
Websitehttps://jedfox.com
Observablehttps://observablehq.com/@j-f1
GitHubhttps://github.com/j-f1
Twitterhttps://tweets.jedfox.com
@Aaronvegh
1. Open Instruments → Settings → General and toggle “Attach supporting files” on. Note: this increases the size of .trace files, so you should turn it back off when you’re done.
2. Reproduce the issue
3. Once Instruments has crashed, open Terminal and run `open -R /private/var/folders/*/*/C/com.apple.dt.Instruments/path_manager/xrtmp__*/*.trace/*.run/Attachments/trace-data.atrc`. This will open a Finder window with a `trace-data.atrc` file selected.
@Aaronvegh Oh no! I don’t think the Instruments team is aware of any crashes in the Hitches instrument. Can you report it using Feedback Assistant? Please attach a sysdiagnose and a trace-data.atrc file collected using these steps:
@mattro Please send us a report using Feedback Assistant if it isn’t fixed in the 26.4 betas — we’d love to take a look!

The Xcode 26.4 beta is out with some really cool features in Instruments! Instruments now has a new Run Comparison feature that allows you to compare call trees across runs so you can quickly verify your performance optimizations (or catch any regressions).

We also have a new Top Functions mode. This new top level mode on the call tree makes it really easy to identify the most expensive functions in the trace no matter where they are called from.

Best part is that these features can be used together to help you optimize your code!

Full release notes: https://developer.apple.com/documentation/xcode-release-notes/xcode-26_4-release-notes

Xcode 26.4 Beta Release Notes | Apple Developer Documentation

Update your apps to use new features, and test your apps against API changes.

Apple Developer Documentation
@davedelong @stroughtonsmith Make sure you’re signed up for “Meet with Apple” emails here. They announce upcoming activities like this one. https://developer.apple.com/account#EmailsCard
Sign In - Apple

Sign in to your Apple Account

@kylebshr you have to put the HStacks in before you pass the view to Group(subviews:)
@kylebshr This happens because you’re allowed to return multiple subviews from your `Item` view, and then have the `Group(subviews:)` modify each one independently. There’s a similar conundrum with `backgroundProminence` in the environment and the approach documented there should help with your environment property too: https://developer.apple.com/documentation/swiftui/environmentvalues/backgroundprominence
backgroundProminence | Apple Developer Documentation

The prominence of the background underneath views associated with this environment.

Apple Developer Documentation

RE: https://infosec.exchange/@madcoder/115466826731130245

Now I finally understand why thr C++ member initializer syntax is spelled the way it is

@stefanpauwels Got it, so the issue is that the Release configuration uses your App Store bundle ID instead of the development one. One way to avoid this is to set up a Profiling configuration and use that for the Profile mode of your scheme. It’s definitely important to use the other settings of Release that enable optimizations, as you’ll otherwise waste time fixing perf issues that never affected your customers because they’re fixed by compiler optimizations.
@stefanpauwels Hi, Instruments engineer here! I’d be interested to learn more about your issue. We definitely recommend using the Release config to get the most accurate profiling results. What about that causes you to use the production CloudKit environment? Can you report this using Feedback Assistant and attach the newest file revealed by `open -R /var/folders/**/pbxperfconfig.plist` so we can see what options are being passed to Instruments?